Servbase uses an owner-first access model. The primary account owns the applications and can grant scoped access to additional members.
Ownership
Each application belongs to the owner account that created it. That owner controls:
- plan and billing
- app settings
- member invitations
- app deletion and lifecycle actions
Member access model
Current member records support:
- an invited email address
- application scope of
all or specific
- selected application IDs when scope is specific
- selected resource permissions
- status values such as
pending, active, and revoked
Application scope
All applications
The member can access every application in the owner’s workspace scope.
Specific applications
The owner must select at least one owned application for the member.
Resource selection
At least one resource must be selected when inviting or updating a member.
The API validates that selected applications actually belong to the owner. Forged requests with foreign app IDs are rejected.
Member lifecycle
Current member statuses include:
Removing a member deletes the membership record from the owner’s workspace context. 