Connect your company's identity provider to the portal with SAML 2.0, or let users sign in with Google, LinkedIn, Facebook, or X through OAuth. With user provisioning turned on, the portal creates a user the first time someone signs in through your identity provider.
Turn on SAML in the portal's security settings, then add each identity provider's sign-in URL and certificate.
The identity provider identifies each person by their Magentrix username, user ID, or federation ID – you pick which.
Add more than one SAML identity provider to the portal, each set up with its own sign-in URL and certificate.
Show a login button on the sign-in page, labeled with the identity provider's name.
Associate an identity provider with a Custom Hub, so the people who sign in through it land in that hub.
Send users to a page you choose when they log out, or when a sign-in fails.
Turn on user provisioning for a SAML identity provider, and the details it sends at sign-in become a new portal user. You don't have to create each user by hand before they sign in.
The identity provider sends the person's name, email, and username, plus optional fields such as title, phone, language, and time zone.
A role value sets whether the new user is an employee, a partner, or a customer. If no role is sent, the portal uses the default role from your self-registration settings.
For partner and customer users, the portal can create the account and contact, or match existing ones – an account by ID or name, a contact by ID or email.
If no account is sent, the portal can place the user in a default account you set in your self-registration settings.
Turn on Magentrix as a SAML identity provider, then add each application that should accept the portal login.
Enter the application's entity ID and the URL that receives the sign-in, and upload the application's certificate.
Choose the SAML attributes each application receives, built from user fields, functions, or fixed text, which supports creating the user in that application on first sign-in.
Choose which security roles can sign in to each application.
Sign the SAML assertion, encrypt it, or both, for each application.
Magentrix uses OAuth for social logins, for AI tools that work with portal data, and for its connections to Slack, Microsoft Dynamics 365, and SharePoint.
Add each one as an authorization provider in Connected Apps with its OAuth key and secret. Users link the account from their profile, then sign in with it.
External AI assistants register with the portal through OAuth 2.1, and each user chooses whether to allow access. Read and write are separate permissions, and a tool can only do what that user's role allows.
Connect a Slack workspace through OAuth 2.0. Magentrix stores the tokens Slack issues securely, and the granted scopes set what it can do in Slack.
Connect Magentrix to Dynamics 365 and SharePoint through OAuth 2, using an app you register in Microsoft Entra.
Connect your identity provider, create users automatically at first sign-in, and use the portal to sign people in to your other applications.