- Manage users
- Import users from a CSV file
- Make mass changes to user details
- Search for users
- View user details
- Manage dependents
- Manage organization subscriptions
- Manage user attributes
- View a list of user attributes
- Out-of-the-box user attributes
- Create a user attribute
- Edit a user attribute
- Prevent users from editing System Setup attributes
- Delete a user attribute
- Clear attribute values for all users
- Translate custom attributes
- Automatically disable users based on attributes
- Automatically delete users based on attributes
- Configure an Organizational Hierarchy attribute
- Create a Geo-aware Single-select Picklist attribute
- Manage user authentication
- Enable authentication methods
- Assign authentication methods to applications
- Configure SDK access security
- Enable two-factor authentication
- Enable single sign-on as an authentication method
- Enable single sign-on for Self Service
- Enable single sign-on for the BlackBerry AtHoc management system
- Import a service provider certificate
- Configure identity provider settings
- Configure service provider settings
- SSO logout service
- Export SP and IDP settings
- Import IDP settings
- Import an existing IDP configuration
- Enable SSO certificate revocation list checking
- BlackBerry AtHoc Customer Support Portal
- Documentation feedback
- BlackBerry Docs
- BlackBerry AtHoc
- 7.18
- Manage Users
- Manage dependents
- Import dependent users
Import dependent users
To import dependent users, include the username of the sponsor in a Sponsor column in the import CSV file.
The following conditions apply to importing dependent users with a CSV file:
- The dependents feature must be enabled for your organization.
- The username of the sponsor must already exist in theBlackBerry AtHocsystem before attempting the import.
- You cannot import a user as a dependent if they are already in the system as a sponsor.
- Dependents can only be imported into the organization of their sponsor.
- Dependents must have unique usernames in theBlackBerry AtHocsystem.
- If partial user import is enabled and there is an error in the sponsor user row, the dependent user is imported as a standalone user, not as a dependent of the sponsor.
- You can change the sponsor of a dependent to another sponsor in theBlackBerry AtHocsystem.
- You can change a sponsor user into a dependent user by setting their sponsor attribute to the username of another sponsor user.
- You cannot import both the organization attribute and the sponsor attribute in the same file. This prevents a dependent from being created in a different organization than their sponsor.
- You can import dependent users from the suborganization, enterprise, or super enterprise level.