For the complete documentation index, see llms.txt. This page is also available as Markdown.

Teams

The Teams section helps you control who can access your organization, and what each member can do.

Team management capabilities

In Teams, you can:

  • view all organization members,

  • invite/add new members,

  • remove members,

  • update member role and access scope,

  • control workspace-level access,

  • control private chat eligibility based on permissions.

Typical role model

Flashgate uses role-based access control. Common role levels include:

  • USER: basic usage

  • BILLING: billing/subscription operations

  • WORKSPACES: workspace and team operations

  • ADMINISTRATOR: administrative settings and user management

  • OWNER: full control

Workspace and private chat access

For production setups, team governance should include:

  • explicit workspace assignment,

  • least-privilege role configuration,

  • periodic review of access to repositories and private chat environments.

Operational recommendations

  • Add members with the minimum role needed.

  • Use ADMINISTRATOR/OWNER roles sparingly.

  • Remove inactive users quickly.

  • Re-check permissions after org restructures.

API mapping

  • GET /organization/users

  • POST /organization/users

  • GET /organization/users/{userId}

  • PUT /organization/users/{userId}

  • DELETE /organization/users/{userId}

  • POST /organization/users/{userId}/activate

See: Organization Management API

Last updated

Was this helpful?