Repository navigation
docs: clarify teams, workspaces, and administration roles - #1067
Open
rachaelrenk wants to merge 14 commits into
Open
rachaelrenk wants to merge 14 commits into
rachaelrenk wants to merge 14 commits into
Conversation
Unify team membership, roles, and Admin Panel guidance; preserve Enterprise workspace scope and plan-qualified factory access. Co-Authored-By: Warp <agent@warp.dev>
Preserve upstream factory worker and Blueprint guidance while retaining canonical administration links. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
Terminology review record
Detailed provider-specific permissions and lifecycle procedures remain in PR 2. No product settings were changed during verification. |
Add verified browser routes, clarify reporting visibility and billing prerequisites, and fix product-specific invitation handoffs. Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Keep the existing deletion-policy regression on its canonical membership page and remove references to the retired duplicate. Co-Authored-By: Warp <agent@warp.dev>
Relocate the canonical page to /factories/teams/, preserve cross-topic navigation, update internal references, and redirect legacy URLs directly. Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Align workspace descriptions across membership, administration, and billing documentation while keeping SSO details with settings guidance. Co-Authored-By: Warp <agent@warp.dev>
Keep cap types and limit interactions in Enterprise billing; retain workspace administration guidance, links, and the legacy anchor. Co-Authored-By: Warp <agent@warp.dev>
Apply review edits to role and Admin Panel descriptions, keep factory-role eligibility local, and distinguish Warp Terminal plans from Warp Factories plans while preserving heading anchors. Co-Authored-By: Warp <agent@warp.dev>
Keep Factories and Enterprise sidebar shortcuts, redirect the former Factories URL, and preserve the refined content and legacy anchors. Co-Authored-By: Warp <agent@warp.dev>
rachaelrenk
marked this pull request as ready for review
November 20, 2026 17:21
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this feature does
Teams share factories and other resources, while roles determine who can administer them. This documentation change standardizes terms and gives self-serve customers team-first guidance and distinguishes Enterprise workspace administration from team and factory access. It documents existing behavior, not a new product release.
Summary
PR 1 of the teams, workspaces, and factory-access reconciliation. Standardizes team and Enterprise workspace definitions, consolidates administration guidance, and distinguishes membership, administrative roles, factory permissions, and plan conditions.
The membership guide lives under Terminal at
/knowledge-and-collaboration/teams/, with Factories and Enterprise sidebar shortcuts to the same page. The canonical-source map highlights six core topics rather than every related reference. Spending rules now live in Enterprise billing, with authority explained on Workspaces.Provider-specific setup handoffs remain in the separate stacked PR #1071. Moving procedures out of Pricing FAQs is recorded as separate follow-up work.
Changes
Canonical content ownership
These pages own the definitions and rules for teams, workspaces, roles, settings, and plans. Other pages provide the context needed for their task and link here for details.
Primary tab: Terminal; shortcuts: Factories, Enterprise
Tabs: Terminal, Enterprise
Tabs: Enterprise
Tabs: Factories
Tabs: Terminal, Enterprise
Tabs: Support
Billing, integration, and privacy pages remain the owners of their detailed rules; they are supporting references rather than core topics in this map. Current commercial prices remain on Warp pricing.
Plans and administration
Standard capabilities below summarize the owning references; account-specific access can differ. Current prices and commercial terms remain on the pricing and billing surfaces, not in a new purchase table.
Roles and scope
Self-serve team/workspace roles mirror one-to-one; customers manage team roles rather than an independent workspace-role selection. Workspace-role terminology remains Enterprise-facing, except where a literal UI label or a real permission/billing/policy scope needs explanation.
Billing visibility is not one permission: on Scale, non-admins can see their own usage. Eligible active members can purchase shared usage without thereby gaining subscription or payment-management authority. This PR does not infer a general right to view payment-card details from either action.
Content design plan
Editorial verdict: Retain the existing customer tasks while removing competing policy owners. Preserve browser-only administration, ownership-transfer consequences, settings enforcement, and the distinction between provider retention, service-improvement collection, and saved run data. Cross-links supply discovery without creating another documentation space. No new feature, compliance commitment, or provider lifecycle guarantee is introduced.
Validation
mainbefore final validation.npm run typecheck: 0 errors, 7 hints.npm run test:heading-vars: 5 passed.npm run build: 426 pages.npm run test:heading-tocs: 3,686 entries validated.npm run test:homepage-json-ld: passed.git diff --check: passed; working tree clean.Trunk is unavailable locally. Node 25 is outside the package's declared engine range; the checks above completed. Existing build warnings include chunk size, deprecated Markdown configuration, missing/empty i18n data, and the
/404route conflict.Usability validation
The original deployed-preview walkthrough asked 28 JTBD-based questions. After these fixes, a focused retest followed real homepage/sidebar/article links through newly rendered local HTML for the affected tasks; the internal content map and backend source were not navigation shortcuts.
These are text/link usability results, not live-account authorization or provider-consent tests. The deployed preview was stale during the focused walkthrough; a later freshness check confirmed the new membership and role guidance is now served. Visual layout, search-dialog, responsive, accessibility-interaction, and product-account testing remain unperformed.
The provider questions Q13–Q16 were separately retested in PR #1071. Its Azure eligibility question remains an explicit owner-review limitation. The Docs usability validation toolkit has a separate handoff plan and is not implemented in either content PR.
Unverified claims
The first two items apply to
src/content/docs/knowledge-and-collaboration/roles-and-permissions.mdx.Section: “Managing admins.” No production cohort inventory was performed.
Section: “Promoting or demoting admins.” Both paths were inspected in source, not exercised live.
Location:
src/content/docs/enterprise/support-and-resources/billing.mdx, “Workspace spending limits.” The factory UI notice was inspected in source, not observed in a live account.Location:
src/content/docs/factories/quickstart.mdx. This marker is inherited from mergedmain; this PR only retargets the administration link on that page.Documentation risk
Risk: engineering-review-required
Rationale: Consolidates substantive role, plan, billing, administration, and privacy guidance; source checks and maintainer-provided SME confirmation do not replace the listed live-account checks.
Source files consulted: Existing Teams, Admin Panel, roles, factory permissions, privacy, and billing documentation; private implementation references and reviewer evidence are retained in the internal plan, not copied into this public PR.
Requested engineering reviewers: none
Engineering review status: pending
Docs override: none
No single owning engineer resolved for this cross-cutting change, so no reviewer is automatically requested.
Related issues
No issue number supplied. This follows the maintainer-led teams, workspaces, and factory-access review.
Follow-ups
Agent artifacts
Co-Authored-By: Warp agent@warp.dev