OKTA ยท STEP-BY-STEP SETUP Production setup tutorial. Trustmi token screens use the real product component with offline teaching data and a deliberately invalid token. Okta screens are reviewed read-only excerpts. Provider-neutral connection cards are examples; field names vary by provider. 00:08 Open your SCIM settings Sign in to Trustmi production and select the organization you want to connect. Open Settings, then Identity and Provisioning, and select SCIM Provisioning. In the earlier settings layout, look under Authentication. You need permission to manage provisioning and tokens. If the page or controls are unavailable, ask your Trustmi administrator or Support to enable the required access. 00:37 Enable SCIM and create a token Turn Enable on and check that the status changes to Enabled. Copy the production endpoint shown on the page: api dot trustmi dot A I, slash scim, slash v two. When there is no active token, select Create Token. If a token is already active, coordinate with its owner before replacing it. A replacement invalidates the previous token and must be coordinated with the connector update. This demonstration uses local teaching data and does not change a real organization. 01:13 Copy the full token now After creating the token, find the highlighted panel that says Copy this token now. Select the copy button beside the full token and save the value in your approved secret store. The full token is shown only once. The Token ID below it is an identifier and cannot authenticate your connector. The value on this screen is deliberately invalid and is only a teaching example. 01:41 Add Trustmi in Okta In Okta Admin Console, open Applications and Browse App Catalog. Search for Trustmi, open the approved integration, and select Add Integration. Complete the application setup, then open its Provisioning tab. If you already have a Trustmi application, first confirm that the tab is available. Keep your existing sign-in configuration; SCIM provisioning is configured separately. Contact Trustmi Support if the approved integration or Provisioning tab is unavailable. 02:17 Paste the token and test Open Provisioning, then Integration, and select Configure API Integration. Enable API Integration and paste the full Trustmi token into API Token. Enter only the token value, without the word Bearer. If the application displays a base URL field, enter the production endpoint copied from Trustmi. Select Test API Credentials. Resolve any error before selecting Save. Leave Import Groups off unless you need to discover existing groups. 02:53 Enable the lifecycle actions Open Provisioning, To App, and select Edit. Enable Create Users, Update User Attributes, and Deactivate Users. Disable password synchronization, including Set password when creating new users if that option appears. Save your changes. Trustmi does not use SCIM password synchronization. The screen excerpt shows the lifecycle controls; review the password settings separately before saving. 03:25 Review the user mappings Review the attribute mappings in the same To App section. For initial onboarding, use the intended Trustmi sign-in email as the application username and primary email. In the SCIM-only application, these values come from Okta user dot login and user dot email. If they differ, agree the mapping with Trustmi Support before assigning users. Map first name, last name, title, department and division as needed. Department and division do not assign organizational units. Do not map passwords, manager, roles or permissions. 04:07 Assign and verify one pilot Open Assignments and assign one agreed pilot identity to the Trustmi application. Check the provisioning task result, then confirm the correct account in Trustmi. Change a supported profile field, such as title, and verify the update. Match existing accounts before allowing creation. If you receive a conflict, review the existing account with Support instead of deleting it or creating another identity. 04:37 Push the pilot group After the pilot users are provisioned, open Push Groups. Select Push Groups, then Find groups by name, and select the agreed pilot group. Use separate groups for application assignment and Group Push. Review matching carefully before linking an existing organizational unit. Complete the group push, then verify the resulting Trustmi organizational unit and its members. Adding or removing members changes organizational-unit access. 05:10 Validate, then expand Before expanding assignments, verify membership additions and removals and deactivate and reactivate the same pilot account. Have a Trustmi administrator check the resulting roles, permissions and organizational-unit access. Review failed provisioning tasks and confirm that no duplicate accounts were created. Once these checks pass, expand in agreed stages. For help, share the task reference and a sanitized error with Trustmi Support. Never send the token or an Authorization header.