Organization settings

Navigate to Organization (gear icon or sidebar link) inside your org slug. Sub-pages include General, Schedule, Members, Teams, Permissions, Statistics, Scoring, Billing, Exports, and Developer (when your plan allows API access).

Only Owners can rename or delete the organization. Admins manage integrations, most settings, and invitations. Members and Viewers consume monitoring surfaces according to role.

Organization → General sets the display name shown in the shell, emails, and exports. Names must be 2–120 characters. The URL slug is assigned at creation and is not changed from this screen.

Owners can delete the organization from General — a destructive action that removes org data subject to retention and legal holds.

Organization → Schedule controls the organization calendar used everywhere:

• IANA timezone— “today,” week boundaries, and report months.
• Week start day — aligns monitoring week columns and weekly reports (Sunday vs Monday, etc.).
• Fair totals policy — excluded weekdays, minimum logged-day minutes, and whether to hide excluded days in monitoring grids. See fair totals.
• Work hours window — optional active-day bounds for presence and break math.

Set schedule before your first weekly report — changing timezone later shifts historical bucket boundaries.

Organization → Members lists login accounts, pending invitations, and seat usage against your plan.

• Owner — billing, deletion, and full admin capabilities.
• Admin — integrations, settings, people management; cannot delete the org.
• Member — standard access to monitoring, people, and reports.
• Viewer — read-oriented access (exact scopes evolve with granular permissions).

Invitations send email links; accepted members map to worker seats when activity monitoring applies to them. See People & profiles for the worker directory versus member accounts.

Organization → Permissions will expose fine-grained scopes per membership (monitoring, people, integrations, scores). Today, access is primarily role-driven via @people/auth RBAC on the server.

Feature flags and plan gates (API access, AI agents, export limits) apply at the organization level — a Member cannot bypass a plan limit by role alone.

Organization → Teams creates and renames teams, assigns slugs, and manages membership lists. Teams power the team= filter on Monitoring and Reports.

Plan limits cap the number of teams (e.g. 3 on Hobby, 20 on paid tiers in the product catalog). Person profiles assign workers to teams defined here — they do not create new teams.

• Statistics — which metrics appear on dashboards and feed SPACE.
• SPACE scoring — enable dimensions, benchmarks, alerts.
• Billing & retention — plan, seats, history windows.
• Integrations — connect Slack, GitHub, Jira, and developer apps.