Sharing & Collaboration

Gnoll supports team collaboration at two levels: organizations and projects. Invite teammates, assign roles, and control who can see and edit your work.

Organizations

An organization is the top-level container for all your work. Every user belongs to at least one organization, and all projects, issues, and API keys are scoped to an org.

When you sign up, a default organization is created for you automatically. You can invite others to join it, or create additional organizations.

Roles

Members can have one of three roles, each granting different levels of access:

Role	Permissions
`Admin`	Full access — manage members, settings, API keys, billing, and all projects/issues
`Member`	Create and edit issues, manage projects, use API keys
`Viewer`	Read-only access to issues, projects, and dashboards

Inviting Members to an Organization

Only Admins can invite new members. To invite someone:

Go to Settings and find the Members section.

Enter the person's email address, display name, and choose a role.

Click Invite. If the person already has a Gnoll account, they are added immediately. Otherwise, an account is created and they receive an email invitation.

Plan limits apply. The number of members you can invite depends on your plan. Free plans support up to 5 users, Team up to 25, and Business is unlimited.

Via the API

POST /api/v1/org/invite

{
  "email": "teammate@example.com",
  "displayName": "Jane Doe",
  "role": "Member"
}

Requires the Admin role. Returns the new member's details on success.

Managing Organization Members

GET /api/v1/org/members

Lists all members of the current organization with their roles and join dates.

PATCH /api/v1/org/members/{userId}

Update a member's role. Only Admins can change roles.

DELETE /api/v1/org/members/{userId}

Remove a member from the organization. Only Admins can remove members.

Sharing Projects

Projects live inside organizations. By default, all org members can see all projects. You can additionally invite specific users to individual projects with project-level roles.

Inviting Members to a Project

POST /api/v1/projects/{projectId}/members/invite

{
  "email": "colleague@example.com",
  "displayName": "John Smith",
  "role": "Member"
}

Managing Project Members

GET /api/v1/projects/{projectId}/members

Lists all members of a specific project.

PATCH /api/v1/projects/{projectId}/members/{memberId}

Update a project member's role.

DELETE /api/v1/projects/{projectId}/members/{memberId}

Remove a member from a project.

Best Practices

Use organization-level membership for teammates who need access to everything.
Use project-level membership when you want to give someone access to a specific project only.
Assign the Viewer role to stakeholders who need visibility but should not modify issues.
Keep the number of Admins small — Admins can manage billing, members, and all settings.