Members
A member is defined as the connection between a Redivis user and your organization. Members are the group of users who have been approved to join your organization, after having submitted an application to verify their identity via their login credentials.
In the Members section of the administrator panel, you can view a filterable, downloadable list of all members. You can also invite new members to your organization from this page.
If a member (or pending member) requires administrator action (e.g., membership approval, requirement approval, restriction exception approval) there will be an alert next to their name. To view information about a member, and respond to their access requests, double click on the member.
View members in the administrator panel. Access requests will show with an alert.
On a member's overview tab, you can view information about the user's identity and their interactions with your organization. Public information such as the user's name and ORCID iD is available, as well as information about the authentication mechanism they use to interface with your organization and any approved datasets.
Membership can be revoked at any time by clicking the Manage button at the member's page. If a user's membership is not approved, they won't be able to access any restricted data in your organization.
If a user is an administrator, they will be marked with labeled as such throughout the admin panel. You can also manage all administrators for your organization the settings panel.
When a user applies to join your organization, they must choose one of their verified identities to associate with this membership — either an institutional login via SSO, a Google login, or other email address. This allows administrators to establish confidence that the user is who they say they are, and binds the security of their access to your data with a particular identity provider.
Users are encouraged to bind multiple authentications to their account so that they have a pathway to recover work when moving between institutions. However, a member must log in with their approved authentication method before they can access any of your organization's restricted data. If they lose access to their approved authentication, they will need to submit a request to update their membership with a new authentication method, which can then be approved or rejected by an administrator.
This approach makes it trivial to allow a researcher to continue their work when moving between institutions, avoiding common pitfalls as researchers move throughout their academic career. However, it also ensures that access is promptly revoked as soon as an individual loses their current institutional credentials — it is at administrators' sole discretion whether to approve a new authentication for an existing member.
You can control your membership settings, such as the preferred identity authentication method and authentication timeout period in the Membership tab of your organization settings.
Members must log in through their approved identity provider before accessing restricted data.
You can resolve all access requests for the given member on the Requirement approvals tab. Additionally, you may add, complete, and approve any additional requirements here on behalf of the user — facilitating new user onboarding when moving from existing access systems.
On the access overview tab, you can view a comprehensive list of a member's access to all of your organization's datasets. This list allows you to audit that the member has the ability to interact with the datasets that you expect.
When users request approval for data exports, their submissions will appear on this tab of their member profile. You will see an alert symbol next to the tab and on any submissions needing approval.
You will manage these in a similar way to requirement approvals. However, you can't generate a restriction exception on behalf of a user.
Last modified 5d ago