Guidal
Sign in

Organizations and members

Invite people, assign roles, and manage access to your projects.

An organization owns everything: projects, services, billing and people. You get one when you sign up, and anyone you invite joins it.

Invite someone

bash
guidal members invite someone@example.com --role developer

They receive an email with a join link. Until they accept, the invitation shows as pending:

bash
guidal members invites

Withdraw one that has not been accepted:

bash
guidal members revoke someone@example.com

See who has access

bash
guidal members list

Roles

Roles determine what a member can do.

Owner has full control, including billing and deleting the organization.

Admin manages projects, services and members, but not billing or the organization itself.

Developer deploys and operates services — the day-to-day role for most engineers.

Viewer has read-only access. Useful for stakeholders who want to see status without the ability to change anything.

Change someone's role:

bash
guidal members role someone@example.com --role admin

Grant the narrowest role that lets someone do their job. Most engineers need Developer, not Admin — and an account compromised at Viewer level is a very different incident from one compromised at Owner.

Remove someone

bash
guidal members remove someone@example.com

Access ends immediately. Also revoke any API keys they created — those authenticate independently of their account, so a key outlives the person unless you delete it.

Leave an organization

bash
guidal members leave

An organization must keep at least one owner, so the last owner cannot leave. Transfer ownership first.

In the dashboard

  1. In the navigation pane, choose Settings, then Organization.
  2. Choose the Members tab.
  3. Choose Invite member, enter the email address and select a role.
  4. To change a role, choose the member and select a new role.

Member limits

PlanMax members
Starter5
Pro25
Team100

Pending invitations count toward the limit. If an invite is refused because you are at the cap, revoking stale pending invitations usually frees room.

Projects and access

Members belong to the organization and can access its projects according to their role. Projects are an isolation boundary for resources — a service in staging cannot reach a database in production — not a per-person permission boundary.