Skip to main content
Admin Portal provides three different sign-in options to cater to your organization’s needs and preferences. These options are designed to provide convenience and security for users accessing the portal. Access the sign-in page at the Admin Portal.
Access the unified Portal to manage applications, organization configuration, and secure administrator access. This guide covers current sign‑in methods (Email & SAML SSO), rollout, and operational best practices. Google sign-in has been deprecated (@gmail domain).
Google sign-in (@gmail domain) has been deprecated and is no longer available. Migrate any residual flows to SAML SSO or Email + Password.

Email Login

Baseline credential access

SAML SSO

Centralized identity & governance

Provision

Auto user creation via SSO

Migrate

Link legacy accounts

Audit

Track access changes

Resilience

Maintain break‑glass account

Sign-In Options

  • Email & Password
  • SAML SSO
Direct portal credentials (use for initial access or controlled break‑glass fallback).

SSO (SAML) Enablement Workflow

1

Engage Support

Contact support with org domain & desired scope (all users or whitelist subset).
2

Configure IdP

Set Assertion Consumer (Response) URL: https://amity-portal-prod-auth.amity.co/saml2/idpresponse
3

Audience Restriction

urn:amazon:cognito:sp:eu-central-1_gcJoCA15K
5

Domain Sign-In

Users choose “Sign in with SSO”, enter org domain, redirected to IdP.
6

User Migration

Existing portal accounts linked to SSO identities post first successful SAML assertion.
Delete legacy direct admin accounts before activation if you want to strictly enforce SSO-only access.

Post-SSO Behavior

New SSO-authenticated users are created with default access model on first login.
Manual creation in Console is restricted to prevent identity fragmentation.
Existing non-SSO accounts remain functional unless explicitly removed.
Central revocation at IdP immediately prevents portal access.

Migration Tips

  • Before Enablement
  • During Cutover
  • After Enablement
Inventory current admin users; decide which persist; communicate cutover date.

Metrics & Monitoring

MetricPurposeHealthy SignalAction Trigger
First Login Success %Onboarding friction≥ 95%Drop → review IdP attribute mapping
Legacy Account CountProgress toward full SSO adoptionTrending to 0Flat > 0 for 2 cycles → enforce cleanup
SSO Provision TimeAutomation latency< 30sDelays → check webhook / IdP latency
Failed SAML AssertionsDetect config issuesNear 0Spike → validate Audience / ACS URL
Duplicate EmailsIdentity collision0Any → merge / remove stale account

Troubleshooting

IssueLikely CauseResolution
SSO option not shownOrg not enabledConfirm enablement with support
Assertion Consumer mismatchWrong ACS URLUpdate IdP to official URL
Audience validation errorIncorrect Audience stringUse urn:amazon:cognito:sp:eu-central-1_gcJoCA15K
User loops back to loginAttribute (email) not mappedMap email claim correctly
Duplicate account createdCase variation in emailNormalize email casing & merge
Cannot remove legacy accountStill active sessionsTerminate sessions then delete

Best Practices

Leverage IdP groups to scope admin roles (avoid broad default grants).
Quarterly audit of active SSO users vs HR roster.
Maintain one monitored credential account for emergency (rotate often).
Notify administrators of SSO switch ahead of time with clear rollback steps.
Integrate portal login events into SIEM for anomaly detection.
If you need assistance validating your SAML metadata, contact support with the IdP entityID and certificate fingerprint.