Users & permissions

Hamstik authorization is based on the user’s current Organization membership and role. The app checks access near the data source, so a hidden navigation item is not the security boundary.

Organization roles

• Owner has full responsibility for the Organization.
• Administrator can manage available Organization administration controls, including members and settings.
• Member can work in Projects available to the Organization membership.

See the roles and permissions reference for the compact reference table.

Invitations and membership changes

Inviting a person proposes a role; accepting the invitation creates the membership. Removing a membership takes effect for browser access and existing API credentials.

API access is not a second permission system

Public API access is the intersection of:

1. the user’s current membership and role;
2. the Personal Access Token scopes;
3. the token’s Organization or Project restrictions; and
4. Organization state, including suspension.

A PAT never grants membership by itself. Start with API authentication and PAT scopes for the automation model.