Note: We have confirmed that SAML SSO is possible on various mobile browsers; however, since the Free Plan we tested does not support mobile use, we have not performed actual operation verification.

TrustLogin Admin Page Settings

1. Log in to TrustLogin, open the "Admin Page > App" menu, and click the "Register App" button at the top right of the screen.
   
   
   
2. On the "Register Corporate App" screen, search for and select "Celonis (SAML)".
   
   
   
3. Download the metadata from the "Download Metadata" button in the "Identity Provider Information" section.
   

Now, switch to configuring Celonis.
Do not click the "Register" button yet — open Celonis in a separate window.

Celonis Configuration

1. Open "Admin & Settings > Single Sign-On" and click "Add SSO Provider > SAML".
   
   
   
2. Set any SAML configuration name you like (e.g., TrustLogin) in "General Settings > Name".
   
   
   
3. Open the "Metadata" tab, upload the metadata obtained from TrustLogin, and save by clicking "Save".
   
   
   
4. Click "Download SP Metadata" to download the metadata.
   

Now return to the TrustLogin Admin Page again.

TrustLogin Admin Page Settings (Continued)

1. Upload the metadata downloaded from Celonis to the metadata field in "Service Provider Settings".
   
   
   
2. Save by clicking the "Register" button.

TrustLogin User Settings

① When a User Adds the App via My Page

1. Click the "Add App" button on "My Page".
2. On the "App Registration" screen, select "Celonis (SAML)" and click the "Next" button at the top right of the screen.
3. If you want to change the "Display Name", enter it, then click the "Register" button.

② When an Administrator Adds Members

1. Search for and click the "Celonis (SAML)" app in the "Admin Page > App" menu.
2. Click "Add Member", select the user to add from the member list, and click the "Register" button to add them.

Now return to Celonis.

Celonis Configuration (Enable SSO)

Check the radio button for the SSO provider configuration you created, and click "Activate".
At this point, the administrator and all team users will be forcibly logged out. The administrator will also see an error screen and will need to log in again.