Repository navigation
docs: clarify factory integration setup prerequisites - #1071
Draft
rachaelrenk wants to merge 1 commit into
Draft
rachaelrenk wants to merge 1 commit into
rachaelrenk wants to merge 1 commit into
Conversation
Put actor prerequisites beside setup, distinguish shared and per-factory Slack authorization, and index Azure DevOps without inventing a scope inventory. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Factory setup separates shared integration authorization, attaching an existing connection, and linking a personal account. These updates put the responsible Warp and provider administrators beside setup steps, explain Slack's manager-first prerequisite, and make Azure DevOps permissions guidance discoverable. This documents existing setup paths, not a new feature release.
Summary
PR 2 of the teams, workspaces, and factory-access work, kept separate from #1067 as requested.
Stacked base:
rrenk/teams-workspaces-roles(#1067), notmain. Merge the base first and retarget this PR afterward. Only seven public documentation pages differ from that base; the usability-toolkit governance work is not implemented here.Changes
Content design plan
Reader and job: A factory Editor or team administrator connecting an existing factory to a service, possibly needing another person to approve access.
Gap: The reference definitions explain roles, but connection steps omit the necessary actor or shared-setup dependency. A reader can reach the right page yet still hit an avoidable authorization dead end.
Change: Correct and extend the existing connection procedures and permission index with short prerequisites, links, and handoffs. Preserve provider inventories and avoid a new permission matrix, new public pages, or unconfirmed guarantees about every reconnect/delegation path.
Usability validation
Retested the newly generated local HTML, starting at the homepage and following Factory quickstart → Connect your factory → provider guides and the permission index. This was a rendered text/link walkthrough, not a logged-in product test.
All selected new role, manager, personal-link, and Azure inventory anchors were present in the built HTML. Absolute cross-space links were resolved against the local proposed tree for this retest, not silently followed into older production content.
Validation
npm run typecheck: 0 errors, 7 hints.git diff --check: passed.Inherited length exceptions
Slack, Jira, and GitLab already exceed the combined-page budget. Their before/after word counts are 2,240 → 2,349; 1,691 → 1,751; and 1,563 → 1,592, respectively. The added material supplies prerequisites and actor handoffs; removing valid provider inventories or unrelated workflows to meet a budget would broaden this correction and lose useful information. These inherited overages remain explicit review findings, not an all-pass compression claim. No callouts or public pages were added. Connect your factory, Azure, and the general roles page remain within budget; the permissions index is a reference.
Local Node 25 is outside the declared package engine range; checks completed. Trunk is unavailable. No product settings, integration installations, credentials, or billing were changed.
Unverified claims
The repository contract checker can include markers inherited from the stacked base when comparing against
main. They remain listed here, although these are not new PR 2 claims:Base role reference, “Managing admins.”
Base role reference, “Promoting or demoting admins.”
Base workspace reference, “Workspace spend limits.”
Base factory quickstart; its existing live-preview marker is unchanged.
Documentation risk
Risk: engineering-review-required
Rationale: Changes integration prerequisites and actor handoffs; live consent is untested and Azure/Jira policy reconciliation and inherited length exceptions remain explicit.
Source files consulted: Existing factory connection and provider guides, human/factory role references, and private implementation evidence retained in the internal plan.
Requested engineering reviewers: none
Engineering review status: pending
Docs override: none
Ownership lookup spans multiple engineers, so no reviewer is automatically requested.
Follow-ups
Agent artifacts
Co-Authored-By: Warp agent@warp.dev