Skip to content

docs(enterprise): add organization roles guide - #94

Merged
factory-austin merged 1 commit into
mainfrom
austin/org-role-docs
Nov 11, 2026
Merged

factory-austin merged 1 commit into
mainfrom
austin/org-role-docs

Conversation

@factory-austin

Copy link
Copy Markdown
Contributor

Summary

Adds an Organization Roles page to the enterprise docs explaining the difference between the User, Manager, and Owner membership roles in a Factory organization, what each role can and cannot do, and that exact access varies by plan, enabled features, and administrative settings.

  • New page docs/enterprise/organization-roles.mdx, registered in the Identity & Governance nav group in docs/docs.json.
  • Cross-linked from enterprise/identity-and-access.mdx (to distinguish membership roles from the IdP/RBAC configuration roles discussed there) and from enterprise/service-accounts.mdx (which already referenced "managers and owners" without a target).
  • Content is the draft refined in the Linear ticket (Nikita Lilichenko's "Organization Role Overview", reworked after review feedback to drop "generally" wording and call out the plan/features/admin-settings caveat).

Closes PLT-249

Validation

  • docs.json parses as valid JSON; all 250 nav entries resolve to files on disk (including the new page).
  • Every internal link added or touched resolves to an existing .mdx file (verified with a path check across organization-roles, identity-and-access, and service-accounts).
  • Reconciled against product ground truth in factory-mono: exactly three WorkOS membership roles user/manager/owner (packages/common/src/organization/enums.ts), role privilege is hierarchical Owner >= Manager >= User (packages/frontend/src/auth/utils/hasAdequateRolePrivilege), and the restrictApiKeyCreationToManagers org setting referenced by the draft exists in the settings schema.
  • Docs-only change: no runtime code, no API changes, no auth/entitlement changes.

Notes

  • The page deliberately stays summary-level (per the ticket draft) rather than enumerating every permission, with the plan/features/admin-settings caveat as requested.

Add an Organization Roles page documenting the User, Manager, and Owner
membership roles, what each can and cannot do, and that exact access
varies by plan, enabled features, and administrative settings. Register
it in the Identity & Governance nav group and cross-link it from
Identity & Access and Service Accounts.

Closes PLT-249

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@factory-droid

factory-droid Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Droid finished @factory-austin's task —— View job


No candidate findings were submitted for validation. The full PR diff and existing comments were read; there are no inline comments to post.

0 inline comments posted

@factory-austin
factory-austin merged commit 00fd131 into main Nov 11, 2026
1 check passed
@factory-austin
factory-austin deleted the austin/org-role-docs branch November 11, 2026 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant