User Management - myantandco/RA-BitnobiPilotJuly2020 GitHub Wiki

• a user can create his/her own Bitnobi account by going to the main Bitnobi page, pressing the "Create one here" link and filling in the profile details.
• alteratively the admin user can do this on the user's behalf and the email them with the new userid. The new user can then use the "forgot password" link to reset their password.
• an admin can also use the bulk-user-create.sh Command Line Tool (located in the ~ra-bitnobi/tools folder) to create multiple users at once from a comma-separated values (.csv) file
• each time a new user is create, an email is sent to the admin user.

The admin has the power to enable or disable a user at any time. When a user is “disabled”, Bitnobi will reject that user’s login requests. When a new account is created it must first be enabled before the user can login. If an existing user is “disabled” Bitnobi will retain all of the user’s workflows, policies, result sets, etc. As soon as the user is "enabled" again all of this work is then available to the user.

1. in the "Admin" section, go to the "User Attributes Management" page,
2. click "Options" beside the target user, then select or unselect the "Enabled" checkbox
3. click “Save” when prompted to confirm the change

The admin can set an expiry date for a user. Once the expiry date passes, Bitnobi will automatically mark this user as “Inactive”. By default the expiry date field is blank (i.e. never expires). Once an expiry date has been set, it can be update as required but cannot be deleted. The steps for setting expiry date are:

1. in the "Admin" section, go to the "User Attributes Management" page,
2. click "Options" beside the target user, then select or unselect the "Enabled" checkbox
3. click “Save” when prompted to confirm the change

User attributes determine which resources and datasets that a user can access through matching policies. Attributes and values can be chosen and configured to suit the setup of any organization. Some common attributes include organization, role, department, project, etc.

Note: Both attributes and values are case sensitive

1. navigate to the “Admin > User Attributes Management”.
2. click the “Options” button (⋯) beside the target user and select “Edit”.
3. click the “Add Attribute” button.
4. type in an attribute or select from the drop-down menu of existing attributes.
5. type in a value or select from the drop-down menu of existing values for that attribute.
6. click “Add” and then click “Save” to confirm and save the changes.

1. navigate to the “Admin > User Attributes Management”.
2. click the “Options” button (⋯) beside the target user and select “Edit”.
3. click the “Options” button (⋯) beside the attribute you would like to edit.
4. make the desired changes to the attribute and/or value and click “Save” and then “Save” again to confirm the changes.

1. navigate to the “Admin > User Attributes Management”.
2. click the “Options” button (⋯) beside the target user and select “Edit”.
3. click the “Options” button (⋯) beside the target attribute and select “Delete”.
4. click the “Delete” button when prompted and then click “Save” to confirm the change.

Bitnobi resources are allocated to users by admins using policies. Any user that matches the attributes of a policy will be allocated the selected resources.

Note: Resources are additive. If a user matches two policies with different allocated resources, any resource selected in either policy will be allocated to the user.

Resources in Bitnobi include Workflows (Datasources and Operations), Policies, Reports, Data Transfer, and Admin. Admins can allocate any combination of resources to users. Allocating Admin resources to a user grants the user the admin functions (Resources Management, User Attributes Management, Network Management, and Application Registrations).

Follow the steps below to allocate resources to a policy:

1. navigate to the “Admin > Resources Management” page.
2. click the “Options” button (⋯) beside the target policy.
3. select or deselect resources as desired and click “Save” to confirm the changes.
4. any users matching that policy will have access to the allocated resources when they login.