> ## Documentation Index > Fetch the complete documentation index at: https://docs.condense.io/llms.txt > Use this file to discover all available pages before exploring further. # Settings ## Overview The Settings section in Condense provides a centralized location for managing account details, Git integration, organization administration, and workspace-level configurations. It allows authorized users to update personal information, manage organization members and roles, review workspace associations, and monitor member activity across workspaces. ### Settings help: * Keep account and organizational information accessible in one place * Control membership and role assignments within an organization * View and manage workspace details from a single interface * Track user activity in relation to assigned workspaces ## What You Can Do in Settings ### Account Information * View and update personal information, including name and phone number * Email address is displayed but cannot be changed * Review linked Git account information ### Git Login Account Info * Displays linked Git account details for repository-based development * Used for managing version-controlled applications and transforms ### Organization Management * View organization name, organization ID, and created by (Organization Admin) * Invite new members to the organization * Assign or update member roles (Admin or User) * Remove members from the organization * Track user activity within assigned workspaces ### Workspace Management * View all workspaces associated with the organization * Click on a workspace to view detailed information, including: * Members assigned to the workspace * Last active date for each member * Organization Admins can edit workspace names from this page ## Lifecycle and Permissions ### Who Can Access Settings * Account Info: Accessible by all logged-in users (can edit own name and phone) * Git Login Info: Accessible by all logged-in users for their respective git connection * Organization Management: Only Organization Admins can invite, edit roles, or remove members * Workspace Management: Visible to all members; editing workspace name requires Organization Admin privileges ## Roles and Permissions Search Operation Organization Admin User Edit own account name and phone ✅ ✅ Change own email ❌ ❌ View Git login info ✅ ✅ Invite new organization members ✅ ❌ Edit member role ✅ ❌ Remove member from organization ✅ ❌ View workspace details ✅ ✅ Edit workspace name ✅ ❌ View member last active date in workspace ✅ ✅ ### Role descriptions: * Organization Admin: Full administrative control over organization members, roles, and workspace management * User: Standard access to view settings and workspace details, but no administrative privileges ## Managing Members in an Organization ### Add Members 1. Navigate to Settings → Organization 2. Click Invite Member 3. Enter the email address of the user to invite 4. Assign a role (Admin or User) 5. Send invitation ### Change Roles * Organization Admins can update a member’s role at any time * Changes take effect immediately ### Remove Members * Organization Admins can remove members from the organization * Removing a member revokes access to all associated workspaces in the organization. ## Workspace Settings within Organization View From the Settings → Workspace tab, Organization Admins can: * View all organization workspaces * Select a workspace to view associated members and their last active date * Edit the workspace name ### Monitoring and Audit Within Settings, administrators can: * View last active timestamps for each workspace member * Review organization membership and assigned roles ## Best Practices * Keep member roles aligned with actual responsibilities * Regularly review and update organization membership * Track last active dates to identify inactive members * Maintain accurate workspace names for clarity ## Common Pitfalls and How to Avoid Them 1. Trying to change email address 2. Avoidance: Email cannot be edited; contact system administrator if an update is required 3. Removing active members accidentally 4. Avoidance: Confirm with relevant team leads before removing members 5. Assigning all members as Admins 6. Avoidance: Restrict Admin role to users responsible for organization governance ## Related Links * [Workspaces](/condense/condense-app-getting-started/workspaces) * [Applications](/condense/condense-app-getting-started/applications) * [Transforms](/condense/condense-app-getting-started/transforms) * [RBAC Overview](/condense/condense-app-getting-started/role-based-access-control-rbac) [PreviousPipelines](/condense/condense-app-getting-started/pipelines)[NextCondense Support](/condense/condense-app-getting-started/condense-support)