Organisation administration
Manage team identity, member access, projects, and the usage information visible to admins.
On this page
Manage the team’s identity
Use Organisation settings beside the organisation name to change its display information, including the available name/image fields. These controls require management permission.
The organisation rail lets you switch between teams, create an organisation, or view invitations to join another. Keep similarly named teams distinct so members select the intended project and integration scope.
Manage membership and project access
Open Organisation admin to inspect members and the management controls allowed by your role. Admins can manage ordinary membership; ownership and self-management restrictions remain enforced. Suspending an account’s organisation membership is different from deleting its identity.
Use each project’s Members dialog to add existing organisation members as viewer, editor, or manager. Use room settings for private-room access. See members and permissions before granting wider access.
Read usage and capacity
The admin view shows Running now and AI turns this month, alongside configured limits where present. These are application execution counters; they are not your AI provider’s token bill or account balance.
If a limit blocks new work, let active work finish or ask the administrator about the configured allowance. Repeatedly sending the same prompt will not bypass a concurrency or usage limit. AI providers can impose their own additional limits.
Operating a private deployment
End users do not need to install PostgreSQL, Redis, Docker, or the application source. Those belong to server administration.
If you are hosting the platform yourself, start with the repository’s production deployment guide. It covers the server stack, HTTPS/domain setup, environment configuration, migrations, health checks, and deployment. Access to that repository may be required. Use its backup and restore guide for recovery.
Invitation generation requires a valid public website origin. Clerk handles authentication and email verification; Slack and Discord require separate integration configuration. Do not put server secrets or OAuth credentials into shared chat. These user guides do not replace the deployment runbook.