Organisation administration

Organisation administration covers the settings a pip_admin or pic_admin owns: who is on the team, how you are billed, how you are notified, and how you and your integrations authenticate.

Team, roles & invitations

Invite users to your organisation from Team → Invite. Each invite carries a role; the invitee registers through a scoped /register/<token> link. Roles determine what a user can do — see Roles & permissions for the full matrix. An admin can invite editors/subscribers; only an admin manages users, grants, and API keys.

Billing & plan

Your organisation is on a plan tier that maps to a set of entitlements — rate limits, feature access, and usage caps. Review your plan and usage from Settings → Billing. See Plans & limits for what each tier grants and the Plans & billing concept for how usage is metered.

Notifications

PIE notifies your team about events that matter — publishes, grants, workflow tasks, sync results, and account security. Manage delivery preferences (immediate or digest) from your notification settings; the catalog and templates are localized into your enabled languages. Account-security notifications are always on.

API keys

Create API keys for machine-to-machine integrations from the API Keys page. Keys carry scopes and can be marked sandbox (read-only). The secret is shown once — store it securely. Rotate a key to mint a replacement with a grace window, then revoke to invalidate. See the Authentication guide.

SSO & MFA

Enterprise organisations can configure single sign-on and require multi-factor authentication and session policies. Configure SSO connections and enforce MFA from your organisation's security settings; sign-in then honours your SSO and MFA requirements. (Availability depends on your plan and deployment.)

Related

• Getting started for your role — the end-to-end setup path.
• Multi-tenancy concept — how your org is isolated.