Organizations Module

SDK organization, membership, settings, enterprise, and billing helpers.

AuthOS release 0.8.5 TypeScript SDK 0.8.0 Latest-only documentation
Updated Aug 2, 2026
On this page

The sso.organizations module covers tenant administration, organization settings, enterprise integrations, and several operational helper surfaces.

Core methods

  • create(...)
  • list(...)
  • get(orgSlug)
  • select(orgSlug)
  • update(orgSlug, payload)
  • delete(orgSlug)

Member and invitation helpers

  • members.list(...)
  • members.updateRole(...)
  • members.listServiceAccess(...)
  • members.updateServiceAccess(...)
  • members.transferOwnership(...)
  • invitations.create(...), list(...), cancel(...), accept(...)

End-user and audit helpers

  • endUsers.list(...)
  • endUsers.get(...)
  • endUsers.revokeSessions(...)
  • auditLogs.get(...)

Settings and security

  • setSmtp(...), getSmtp(...), deleteSmtp(...)
  • setCustomDomain(...), verifyCustomDomain(...), getDomainConfiguration(...)
  • updateBranding(...), getBranding(...), getPublicBranding(...)
  • riskSettings.get(...), update(...), reset(...)
  • security.getRiskEvents(...)

Billing credentials

billingCredentials.get(...), set(...), and delete(...) manage organization-owned stripe or polar credentials.

Enterprise and integration helpers

  • oauthCredentials.set(...), get(...)
  • webhooks.create(...), list(...), get(...), update(...), delete(...), test(...)
  • scim.createToken(...), listTokens(...), revokeToken(...), deleteToken(...)
  • siem.create(...), list(...), get(...), update(...), delete(...), test(...)
  • roles.list(...), get(...), create(...), update(...), delete(...)

Upstream providers

Current backend support is documented as:

  • upstreamProviders.list(orgSlug)
  • upstreamProviders.get(orgSlug, providerId)
  • upstreamProviders.create(orgSlug, payload)
  • upstreamProviders.update(orgSlug, providerId, payload)
  • upstreamProviders.delete(orgSlug, providerId)

Updates intentionally accept only name and enabled. Rotate credentials by deleting and recreating the provider so secrets are never returned or merged through a general-purpose update response.

Use domain routes and upstream providers together for enterprise email-domain routing.