Managing team members and roles

Every person who signs in to Amendary belongs to a workspace, the shared account where your connected repositories, Notion pages, and review queue live. This page covers how to invite teammates, what sets the owner role apart, and how each member controls their own email notifications.

Roles: member and owner

Amendary recognizes two roles inside a workspace: owner and member.

Any member can do the everyday work: connect a GitHub account or Notion workspace, map pages to repositories, review and approve flagged corrections, and generate documentation. Connecting a new integration is open to everyone on the team, since adding capability carries no risk to the rest of the workspace.

The owner role is reserved for actions that remove capability or spend money:

• Disconnecting a GitHub or Notion connection the whole team relies on
• Managing billing (starting checkout, opening the billing portal, viewing purchase history)
• Creating or revoking read-only API keys
• Turning on automatic application of corrections for the workspace in Settings, available on paid plans

<aside> ✏ Needs verification: the source material doesn't describe a way for an existing member to promote another member to owner or to change their own role from the dashboard. Treat role assignment as fixed at invitation time until you can confirm otherwise in your account.

</aside>

Inviting a teammate

When someone signs in for the first time with a Google or GitHub account, Amendary checks whether they already have a pending invitation waiting for their email address.

• If they have a pending invitation, they're routed to accept it rather than having a new, separate workspace created for them.
• If they have no pending invitation, Amendary creates a brand-new workspace for them automatically, with a 7-day free trial and the owner role.

This means invitations should be sent before your teammate signs in for the first time. If a teammate accidentally creates their own workspace before accepting an invitation, they'll end up as the owner of that separate workspace instead of joining yours.

Result: an invited teammate who signs in after receiving their invitation joins your existing workspace as a member, alongside everyone else already there.

Removing a teammate

An owner can remove a member from the workspace. Once removed, that person's session no longer grants access to the workspace's repositories, pages, or review queue.

<aside> ✏ Needs verification: the exact steps for sending an invitation and removing a member (the on-screen labels and menu locations) aren't available in the material used to write this page. Check your workspace's members list for the current wording before relying on step-by-step instructions here.

</aside>