Current support status
Use the supported sign-in paths
| Path | Current behavior |
|---|---|
| Password sign-in | Users sign in with their Orchestris email and password. |
| Invitation acceptance | A new recipient creates a password; an existing account uses its current password. Groups and the Admin or Member role are applied on acceptance. |
| Password reset | The /reset-password flow requests and confirms a password reset through the configured email delivery path. |
| Orchestris-managed licensed access | Some licensed deployments can receive a signed session from an Orchestris-managed portal. Customers do not configure this as OIDC or SAML; contact Orchestris to confirm whether it applies to a planned deployment. |
- Path
- Password sign-in
- Current behavior
- Users sign in with their Orchestris email and password.
- Path
- Invitation acceptance
- Current behavior
- A new recipient creates a password; an existing account uses its current password. Groups and the Admin or Member role are applied on acceptance.
- Path
- Password reset
- Current behavior
- The /reset-password flow requests and confirms a password reset through the configured email delivery path.
- Path
- Orchestris-managed licensed access
- Current behavior
- Some licensed deployments can receive a signed session from an Orchestris-managed portal. Customers do not configure this as OIDC or SAML; contact Orchestris to confirm whether it applies to a planned deployment.
Plan for an identity requirement
- Use invitations and password reset for current account onboarding and recovery.
- Use groups for model access instead of assuming an external directory group will be synchronized.
- Use Sessions and account-removal controls when access must be revoked.
- If an external identity provider is mandatory, contact Orchestris before deployment and treat the requirement as an availability decision, not a configuration task.