Settings & Workspace Administration

Relevant source files

The following files were used as context for generating this wiki page:

• packages/twenty-front/src/locales/generated/en.ts
• packages/twenty-front/src/modules/settings/billing/SettingsBilling.tsx
• packages/twenty-front/src/pages/settings/SettingsGeneral.tsx
• packages/twenty-shared/src/constants/DocumentationPaths.ts
• packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-design-doc/design-doc-doctrine.md

The Settings & Workspace Administration module in Twenty provides a centralized interface for managing workspace-level configurations, user permissions, billing, and system health. It serves as the administrative backbone of the CRM, allowing authorized users to define how the workspace operates, who has access to specific data, and how the platform integrates with external services.

The administration system is divided into several functional areas, ranging from general workspace identity (subdomains, logos) to complex technical configurations like row-level security (RLS) and custom object modeling. This modular approach ensures that RevOps leads and system administrators can efficiently maintain the CRM environment as the organization scales.

Sources: packages/twenty-front/src/pages/settings/SettingsGeneral.tsx, packages/twenty-front/src/locales/generated/en.ts, packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-design-doc/design-doc-doctrine.md

Workspace Configuration & General Settings

Workspace administration begins with identity and environmental defaults. The SettingsGeneral component manages core workspace metadata, including the workspace name and its public URL structure.

Identity and Appearance

• Subdomain Management: Administrators can update the workspace subdomain or set a custom domain. Changing a subdomain is a significant operation that triggers a logout for all users to ensure session integrity.
• Branding: Allows for the configuration of the workspace logo and basic appearance settings to match the organization's brand.

Regional and System Defaults

The system allows for granular control over how data is presented and processed based on the organization's locale:

• Time and Date: Configuration of date formats, time formats (12h/24h), and timezones.
• Localization: Setting the default currency and country codes for the workspace.
• Calendar Defaults: Definition of the calendar start day and global timing preferences.

Sources: packages/twenty-front/src/pages/settings/SettingsGeneral.tsx:40-100, packages/twenty-front/src/locales/generated/en.ts

Billing & Resource Management

Workspace administration includes comprehensive financial and resource oversight. The SettingsBilling component acts as the primary interface for subscription management.

Subscription Lifecycle

Twenty supports a tiered pricing model (e.g., Pro, Organization, Enterprise). Administrative tasks include:

• Plan Switching: Moving between plans or changing billing intervals (Monthly vs. Yearly). The system handles "prorata" adjustments automatically during these transitions.
• Trial Management: Oversight of trial periods, including tracking expiration dates and managing transitions to paid plans.

Resource Credits

The platform utilizes a credit-based system for high-compute features like Workflows and AI agents.

• Allocation: Admins can configure recurring credit allocations.
• Usage Tracking: The system provides breakdowns of credit consumption by user and by type (AI vs. Workflow).
• Thresholds: Automated alerts and feature gating when credits are exhausted or limits are reached.

Sources: packages/twenty-front/src/modules/settings/billing/SettingsBilling.tsx:1-40, packages/twenty-front/src/locales/generated/en.ts

Component	Description	Derivation
Interval Toggle	Switches between Monthly and Yearly billing cycles.	SettingsBilling.tsx
Credit Tracker	Displays balance and historical consumption of resource credits.	en.ts
Prorata Logic	Calculates costs when upgrading/downgrading mid-cycle.	en.ts

Roles, Permissions & Security

Security administration is governed by a multi-layered permission model that controls access at the object, field, and row levels.

Permission Layers

1. Object-Level: Controls CRUD (Create, Read, Update, Delete) permissions for entire entities (e.g., "Can this role see Opportunities?").
2. Field-Level: Restricts interaction with specific attributes within an object.
3. Row-Level Security (RLS): A plan-gated feature (Organization plan and above) that allows filtering records based on specific predicates (e.g., "Users can only see records they own").

SSO and Authentication

Administrators manage how users enter the workspace:

• SSO Configuration: Support for OIDC and SAML protocols.
• Bypass Rules: Configuration of "SSO Bypass" for specific users to allow traditional email/password login as a fallback.
• MFA/2FA: Enforcing two-factor authentication workspace-wide.
• Approved Domains: Automated user onboarding for individuals with specific email domains.

Sources: packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-design-doc/design-doc-doctrine.md, packages/twenty-front/src/locales/generated/en.ts

Data Model & Metadata Administration

The administration panel allows for the dynamic extension of the CRM's database schema without code changes.

Schema Management

• Standard Objects: Relabeling or extending built-in objects like People, Companies, and Opportunities.
• Custom Objects: Creating entirely new entities for specific business needs (e.g., "Invoices", "Projects").
• Field Factories: Adding custom fields with specific data types (Boolean, Money, Rating, Multi-Select).

Database Performance

Admins have access to index management tools to optimize read performance. The interface warns that while indexes speed up filtering/sorting, they can slow down inserts and updates, encouraging "intent-based" indexing.

Sources: packages/twenty-apps/internal/twenty-partners/src/skills/twenty-partner-design-doc/design-doc-doctrine.md, packages/twenty-front/src/locales/generated/en.ts

Infrastructure & Health

Administration also covers the technical health of the workspace instance.

• Audit Logs: Provides a historical record of object changes, page views, and security events. This feature requires ClickHouse to be configured.
• Maintenance Mode: Allows administrators to schedule maintenance windows and notify users, during which sign-ups and certain operations are disabled.
• Worker Health: Monitoring the execution of background jobs, such as email and calendar synchronization.

Sources: packages/twenty-front/src/locales/generated/en.ts, packages/twenty-shared/src/constants/DocumentationPaths.ts

Conclusion

Settings & Workspace Administration in Twenty is a comprehensive suite that balances user-friendly configuration with deep technical control. By centralizing billing, security, and data modeling, it enables administrators to tailor the CRM environment to complex organizational requirements while maintaining system performance and security.