IAM | Global Rollout

[acarta99]

No description provided.

[acarta99]

@copilot spellcheck my work

[Copilot]

@acarta99 I've opened a new pull request, #90, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

Pull request overview

Adds new IAM documentation pages to the docs site and wires them into the Docsify sidebar, supporting the “IAM | Global Rollout” documentation needs.

Changes:

• Added IAM overview documentation (roles + access rules).
• Added IAM Users and Roles page workflow documentation.
• Updated docs sidebar navigation to include the new IAM section.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.

File	Description
docs/iam/overview.md	Introduces IAM app overview, role definitions, and access constraints.
docs/iam/users.md	Documents the Users page workflows: inviting, deleting, and editing roles.
docs/iam/roles.md	Documents the Roles page workflow for updating role assignments.
docs/_sidebar.md	Adds IAM section links to the documentation sidebar.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Typo: "organzation" should be "organization".

Suggested change

	All users in an organization have access to the IAM application. However, only users with the `PORTAL_ADMIN` role will be able to edit roles, delete users, and invite new users. `PORTAL_ADMINS` cannot edit their own access or delete themselves from an organzation, that needs to be done by another `PORTAL_ADMIN`.
	All users in an organization have access to the IAM application. However, only users with the `PORTAL_ADMIN` role will be able to edit roles, delete users, and invite new users. `PORTAL_ADMINS` cannot edit their own access or delete themselves from an organization, that needs to be done by another `PORTAL_ADMIN`.

[Copilot]

Documentation accuracy: this references PORTAL_ADMINS, but the role listed above (and used elsewhere in the sentence) is PORTAL_ADMIN. To avoid implying a different role constant exists, keep the role name as PORTAL_ADMIN and pluralize outside backticks (e.g., "PORTAL_ADMIN users" / "PORTAL_ADMINs").

Suggested change

	All users in an organization have access to the IAM application. However, only users with the `PORTAL_ADMIN` role will be able to edit roles, delete users, and invite new users. `PORTAL_ADMINS` cannot edit their own access or delete themselves from an organzation, that needs to be done by another `PORTAL_ADMIN`.
	All users in an organization have access to the IAM application. However, only users with the `PORTAL_ADMIN` role will be able to edit roles, delete users, and invite new users. PORTAL_ADMIN users cannot edit their own access or delete themselves from an organzation, that needs to be done by another `PORTAL_ADMIN`.

[kirpaChahal]

Think this looks great overall. The only additional points I’d suggest including are that invite emails no longer expire after 24 hours, since users are now added to the Botcopy organization immediately once granted access, and that more granular permission roles are planned for a future release.