Organizations and teamwork

Organizations manage members, resource scope, permissions and security; they are not reseller status.

Updated 2026-10-01

Before you start

This reference follows current LINK42 pages and permissions. Feature flags, roles, quotas and upstream state govern availability; changing a URL or model name does not bypass authorization.

Select the correct organization context. Authorized managers create/invite; recipients verify organization and role before using resources.

Function / field	Action and purpose	Verification and boundary
Context	Check organization versus personal workspace	Context switching does not grant access.
Invitation	Choose recipient and least role	Sent is not accepted; check state and expiry.
Role / model scope	Grant only needed permissions	Organization policy further constrains member keys.
Remove member	Review resource and active-task impact	Authorization is required; historical bills are not erased.

Use available IP, MFA, model-group and SSO policies. Check continued team access before saving restrictive changes.

Function / field	Action and purpose	Verification and boundary
IP / MFA	Configure actual egress and devices	Organization restrictions also affect sessions/keys.
SSO / SCIM	Require enabled, validated configuration	Saved configuration is not identity-provider acceptance.
Audit	Inspect actor, time and event	Only authorized organization records; sanitize exports.