Organizations & teams
HridaSign is multi-tenant. A user is either independent or belongs to one organization. (A ROLE_PLATFORM_OWNER belongs to none.)
The organization
Created by POST /api/auth/register-company, an Organization carries:
| Field | |
|---|---|
name, domain, logoUrl, description | Identity and branding |
status | TRIAL → ACTIVE / suspended |
plan | FREE, and paid tiers |
maxUsers | Seat limit (default 5) |
maxDocuments | Document limit (default 25) |
A new member cannot be invited past maxUsers; document creation is checked against maxDocuments.
Team management
The org admin works from Team (/team):
| Action | Endpoint |
|---|---|
| List members | GET /api/org/team |
| Invite a member | POST /api/org/team/invite |
| Change a member's role | PUT /api/org/team/{userId}/role |
| Deactivate / reactivate | PUT /api/org/team/{userId}/deactivate · /reactivate |
| The caller's org | GET /api/org/me |
There is no open sign-up into an existing org — a person joins only by invitation. A deactivated member keeps their record but cannot sign in.
The org dashboard
ROLE_ORG_ADMIN lands on OrgAdminDashboard — team activity, document volume against the limit, and plan status. Regular members land on the standard user dashboard, scoped to their own work.
Org plan vs. user tier
Two related but distinct things:
- A user's
subscriptionTiergoverns their personal quota. - An org's
plan/status/ limits govern the whole tenant — seat count, document cap, and whether the org is active at all.
A platform owner can change an org's plan and status from the platform console; an org admin manages people and usage within those bounds.