Admin user actions

admin user overview as an organization management portal admin user , you can v iew applications view and edit users view domains l ogging into the portal important be sure you include the organization management portal outgoing ip address 66 206 202 116 in your list of addresses to be allowed at your end access the portal from one of these urls https //orgmanagementsandbox crbcos com/ (sandbox) https //orgmanagement crbcos com/ (production) dashboard for each type of item (apps, clients, scopes, and so forth) in the network, view a tile showing the number of items that exists for a particular customer to display the dashboard, in the left side icon bar, click dashboard applications within applications, there are scopes and roles scopes provide an organization's applications with access—via the cross river api—to user data this way, they control the abilities and limits (i e , the "scope") of the client application scopes are also known as protected resources roles define what features an organization’s users can see and the permissions they have in the organization's applications an organization can apply roles to different applications use case control access to cr functions and features, for example, p2p user interface each organization is exposed to a subset of scopes and roles for example, a crypto platform might be assigned 5 roles and scopes however, an administrator might choose to let the users within that platform (i e , the organization) see only 3 of those roles and scopes in the applications window, each tile shows both the application name and the display name the back office user has visibility to both names the application user views only the display name also, the card shows the scopes and roles available to the organization suppose a back office user creates a role for which the user's organization does not have access in that case, in that user’s tile, a red red warning indicator will appear next to roles users associate users with an organization; edit user details each user has a name, email, and phone number note that phone number is crucial for enabling user login because it’s used for mfa attempting sign in sends a verification code to the user’s phone (can also be configured for email) at first time sign in, the user decides the mfa method (i e , verify to phone or email) afterwards, if the user wants to change mfa preference, cross river admin intervention is needed the cross river admin verifies that the user provided phone number and email do in fact exist and are valid the admin does this through an external application user interface the ui object (i e , tile) that appears to a user depends on the user’s role the scope associated with that role in the organization in the user view, details on each user appear within a separate tile domains a domain is a group of networked computers that share both user account information and a common security policy user interface sso cross river offers you the option to access cross river applications with your own docid\ qefyw6rrspk79 uzowa o (single sign on) login system benefits of sso include a more seamless and cohesive user experience, as well as higher levels of security we support both oidc and saml configurations sign off to exit the organization management portal, in the upper right corner of the screen, click the person icon; then, click logout