Members
The Members tab is where you invite people to collaborate on your project and manage who has access. Inviting and removing members belongs to the owner — or to anyone whose role carries the Invite / Change roles permission.
Each person you invite gets a role, which decides what they can actually do once they’re in — see Roles & Permissions. New invitations default to Contributor.
Inviting a collaborator
Section titled “Inviting a collaborator”- Type the person’s email into the invite field.
- Pick the role they should get — a built-in one or your own. Leave it as it is for Contributor, the default.
- Click Invite.
What happens next depends on whether they already use Estage:
- They have an Estage account → they’re added immediately.
- They don’t → Genesis emails them a sign-up invitation.
Until they accept, they appear in the list with a Pending badge. You can Resend the invitation at any time.
The access list
Section titled “The access list”The list shows everyone with access — the owner, active members, and pending invites:
| Column | Shows |
|---|---|
| Member | Avatar, name, and email |
| Role | Owner, the member’s role, or Pending — changeable here at any time |
| Via | If access is inherited from a folder, the folder name |
Actions
Section titled “Actions”- Pending invites — Resend.
- Active members — Change role, Gift credits or Remove.
- Folder-inherited members — read-only here; manage them from the folder instead.
- Yourself (if you’re not the owner) — Leave project.
Gifting credits
Section titled “Gifting credits”Click Gift credits on a member to send them AI credits from your balance. Enter an amount and confirm — useful when a collaborator needs to run AI builds on the project.
Removing or leaving
Section titled “Removing or leaving”Removing a member, cancelling an invite, or leaving a project all show a confirmation dialog first. Removing someone revokes their access immediately; their work on the project stays.
Narrowing what a member can reach
Section titled “Narrowing what a member can reach”Access is per-capability and enforced on the server, not merely hidden in the interface: publishing, each Settings tab, the Dedicated Cloud and server, blog content, funnels, and access management itself are separate permissions. See Roles & Permissions.