MSE-80 · Organisation owners and administrators

Organisation owner and administrator guide

Structure and workspaces, members and invitations, roles and permissions, plans and billing, security, integrations, data export and retention, audit, and ending an organisation safely.

Pre-release. Momin OS is in development and is not live. The founder's own organisations are planned to be the first to run on it; organisations outside the ecosystem only at the Enterprise stage. Plan names, prices and quotas are not set. This guide is not a contract; the Terms of Service and any order form prevail.

Label	Meaning
At launch	Planned for the first public release, for the founder's own organisations
Planned	Planned for the release that opens memberships, courses and payments
Later	Planned for the release that runs several ventures as separate organisations
Enterprise	Planned for the stage that opens Momin OS to outside organisations

1. Who runs an organisation

Key pointAn owner should be able to prove at any moment who can do what in the organisation, and why.

The owner is accountable for the organisation's existence, subscription and most consequential decisions. The administrator runs it day to day. Platform administrators are separate: any support access to your organisation is restricted, time-limited, recorded and visible to you.

RuleAuthenticated is not authorised, administrator is not unlimited, read is not export and create is not approve. These rules apply to every person and every AI agent, including the founder.

OAG-D-01. Every organisation is planned to have at least two people able to act as owner. The platform warns an organisation with a single owner.

2. Structure and setup

Level	What it is	Who manages it
Platform	Momin OS itself	The platform team
Tenant	The isolation and commercial boundary: data, plan and billing	The platform team, later self-service
Organisation	A business inside a tenant, with its legal name, currency and members	The organisation owner
Workspace	An optional operational boundary inside an organisation	The organisation administrator

Setting up an organisation

Step 1: Tenant provisioned
Step 2: Organisation created
Step 3: Owner active
Step 4: Policies set
Step 5: Workspaces created
Step 6: Roles reviewed
Step 7: Members invited
Step 8: Integrations connected

OAG-D-02. Two-step verification is required for owners and administrators of every organisation from the day it is enabled, and cannot be switched off for those roles.

3. Members, roles and offboarding

Members join by single-use invitation. For staff and contractors, membership is the last step of joining: no account until the agreement and confidentiality deed are signed, screening is complete and required training is recorded.

OAG-D-03. Every membership held by a contractor, external collaborator or guest has an end date. Access is never extended silently.

OAG-D-04. Roles are assigned on least privilege. A role that grants export, approval or access-changing permissions is assigned only with a recorded reason.

Offboarding a member

Step 1: Membership suspended
Step 2: Sessions and tokens revoked
Step 3: Work reassigned
Step 4: Personal API keys revoked
Step 5: Reason recorded
Step 6: Membership removed when work is clear

OAG-D-05. A leaver's membership is suspended no later than the end of their last working day. No leaver's records are deleted at offboarding.

4. Access reviews

Check	Action if it fails
Every member still works for or with the organisation	Suspend or remove the membership
Every role still matches the member's work	Remove the roles no longer needed
Every privileged role has a recorded reason	Record the reason or remove the role
Every time-limited membership has a current end date	Set or shorten the end date
Every privileged member has two-step verification	Require it before further access
No account has been dormant beyond the set period	Suspend and ask the manager

Each monthly review is recorded: who reviewed, which memberships were confirmed and which were changed.

5. Plans, security and integrations

A plan belongs to the tenant; features are switched by entitlements. When a quota is reached, the platform says so clearly and refuses the action; it never fails silently.

OAG-D-06. A failed subscription payment never deletes or makes unrecoverable an organisation's data. Suspension for non-payment limits use, not ownership.

OAG-D-07. Every API key is scoped to the actions its integration needs, has a named owner and an expiry or rotation date, and is revoked when its owner leaves.

6. Data, audit and ending

The organisation's data belongs to the organisation. Exports need a separate permission, stronger verification, approval for high-risk exports, minimisation and audit. The audit log is append-only: nobody, including the owner, can edit or delete an entry. A legal hold stops disposal until it is lifted.

Deleting an organisation

Step 1: Owner requests deletion
Step 2: Stronger verification and approval
Step 3: Members notified
Step 4: Grace period
Step 5: Data export offered
Step 6: Deletion or anonymisation
Step 7: Records required by law retained

OAG-D-08. No organisation is deleted without its owner's request, stronger verification, an approval, notice to its members and a grace period. An export is offered first.

OAG-D-09. Every import is run first as a dry run with an error report. A contact without recorded marketing consent is imported as not consenting to marketing.

7. Your routine

Cadence	Activity
Daily	Review alerts, pending invitations, approval requests and integration health
Weekly	Review new role assignments, high-risk events and quota usage
Monthly	Access review; subscription invoice, seats and entitlements
Quarterly	Rotate API keys and review integration scopes