Skip to content

PR3: Add admin setup guide for team collaboration#74

Open
ijac13 wants to merge 8 commits intodocs-v3from
pr3-admin-setup
Open

PR3: Add admin setup guide for team collaboration#74
ijac13 wants to merge 8 commits intodocs-v3from
pr3-admin-setup

Conversation

@ijac13
Copy link
Contributor

@ijac13 ijac13 commented Mar 1, 2026

Summary

For admins setting up Recce Cloud for their team. When users sign up, they get one org and one project. After connecting to git, org/project names auto-map from the git provider. Admins can rename and invite team members.

Scope

Path Action Doc Type Notes
3-using-recce/ Create - New section folder
3-using-recce/admin-setup.md Create Tutorial Content from invitation.md + new org management
6-collaboration/invitation.md Delete - Merged into admin-setup.md

Quality Checks

Check Issues Status
QA No issues ✅ Passed
AISEO No issues ✅ Passed
Redirects 1 redirect configured ✅ Complete
Checklist All items verified ✅ Complete

Redirects

Old URL New URL Status
6-collaboration/invitation.md 3-using-recce/admin-setup.md ✅ Added

Content Changes

Before → After

File Before After Review
3-using-recce/ Did not exist New section folder for user workflows ✅ As planned
admin-setup.md Did not exist Full tutorial: Goal, Prerequisites, org rename, project setup, invite members, monorepo setup, Verify Success, Troubleshooting ✅ As planned
invitation.md Basic invitation instructions in Collaboration section Deleted - content absorbed into admin-setup.md with expanded org management ✅ As planned

Review status:

  • ✅ As planned — Change matches migration plan exactly

Change Review

I reviewed all changes and confirm:

  • All CREATE files contain intended new content
  • All DELETE files have content preserved elsewhere or are intentionally removed
  • All MOVE/DELETE actions have redirects configured
  • Navigation updates match the intended structure
  • No unintended changes to other files

Review notes: All changes match migration plan. Redirect added for invitation.md → admin-setup.md.

Test plan

  • Verify navigation links work in local preview
  • Check all cross-references resolve correctly
  • Confirm images render properly

🤖 Generated with Claude Code

ijac13 and others added 5 commits February 27, 2026 21:51
Helps users identify their setup path:
- Own dbt run vs platform (dbt Cloud)
- Simple vs advanced environment

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create 3-using-recce/admin-setup.md: Organization setup tutorial
- Delete 6-collaboration/invitation.md (replaced by admin-setup)
- Update navigation in mkdocs.yml

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@ijac13 ijac13 changed the title docs(v3): Add OSS setup guides and Cloud vs OSS comparison docs(v3): Add admin setup guide for team collaboration Mar 1, 2026
@ijac13 ijac13 changed the title docs(v3): Add admin setup guide for team collaboration Add admin setup guide for team collaboration Mar 1, 2026
@ijac13 ijac13 changed the title Add admin setup guide for team collaboration PR3: Add admin setup guide for team collaboration Mar 1, 2026
ijac13 and others added 3 commits March 2, 2026 14:59
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add step 4 "Rename your project (optional)" with updated instructions
- Renumber "Invite team members" to step 5
- Add step 6 telling admins to inform invitees about acceptance modal
- Remove redundant "Additional Settings > Rename your project" section

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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