Docs

Team Management

Manage organization members, workspace access, roles, and invitations in the FlyDocs portal.

Team management in FlyDocs operates at two levels: the organization and the workspace. Org membership controls who can access the portal. Workspace membership controls who can work on specific projects and use the relay API for those workspaces.

Organization members

Manage org membership from Settings → Members. From here you can invite new members by email and manage existing ones.

There are two org-level roles:

Role Capabilities
Admin Manage connections, billing, org settings, invite and remove members, access all workspaces
Member Access assigned workspaces, generate API keys, use the relay API for projects they belong to

Workspace members

Each workspace has its own member list. Navigate to Workspace → Members to manage who has access.

You can add people in two ways:

  • Add existing org members — select from people already in the organization
  • Invite new members — if someone isn't in the org yet, the portal falls back to an inline org invite. They get added to both the org and the workspace in one step

Members only see projects in workspaces they belong to. This keeps work focused — a frontend team doesn't need to see backend infrastructure projects, and vice versa.

Invitations

When you invite someone by email, they receive an invitation to join the organization. If you invited them from a workspace context, they'll also see pending workspace assignments when they accept.

Pending invitations are visible in the Members section. Admins can resend or revoke invitations that haven't been accepted yet.

Header invite button

Admins see an invite button in the portal header, available from any page. This is a shortcut for adding team members without navigating to settings. The button opens the standard invite flow — enter an email, pick a role, optionally assign to a workspace.

Admin vs member capabilities

The distinction matters most for org-level configuration:

  • Admins manage provider connections, billing, and org settings. They can invite and remove members, create workspaces, and access all projects across the organization
  • Members work within their assigned workspaces. They generate their own API keys, use the relay API for their projects, and see workspace-scoped data only

Both roles use the same CLI experience. The difference is what they can configure in the portal, not how they interact with FlyDocs in their editor.

Next