User Administration
The User Admin section of the App Studio allows an administrator to:
- View, create and update a user's details, be they App users (used in conjunction with our $fh.auth API) or App Studio users
- Batch import users from CSV files
- Assign roles to users
- Associate users to auth policies
- Disable users - rendering them unable to login
- Mark a user for data purge (used with $fh.auth, this flag can be checked to wipe data from a user's app/device)
- Send/re-send an invite email to a user
- Delete Users
Viewing Users
In the User list overview area, details such as the the User's user id, name, email, active status and when they last signed in are shown. There is an option to search for a specific user, which updates automatically as you type. There is an option to create new User's, or edit a specific User. Additional User details are available in the user edit area. Multiple users can be imported from a CSV file using the import users view.
A user also can be deleted from the list view. You have to confirm the deletion before it's actually executed. A user can only be deleted if there are no apps in the studio are created by that user. If there are still apps owned by that user, the deletion will throw an error.
Creating Users
When creating a new user you need to specify the user id. User id is the unique identifier of the user and it has to be unique in your domain and it can not be changed. You will get an error message if the user id is already taken. You can also optionally specify email, name and password for the user. If you want an inivitation email to be sent to the user, you need to specify the email address for the user. You can allow users to specify their own passwords by checking the "Send Invite Email" option.
Roles can be assigned to a new User as well. More details on User Roles is available below.
Users can also be associated with auth policies. That means the user will be automatically added as an "approved" user for a particular auth policy. For more details, please see Managing Auth Policies.
Updating Users
User fields such as their name, email and password can be updated. A User's password cannot be viewed, but it can be set to be a different value. User roles can be viewed and updated in this area. More details on User roles is available below.
A user can be disabled or enabled in this view. Once a user is disabled, that user will not be able to authenticate in $fh.auth API. A special value will be returned by the API to indicate that the user has been disabled.
There is another option here called "Mark for Data Purge". If this option is checked, two things will happen:
- The user will be disabled
- Next time when the user login using $fh.auth, a special value will be returned by the API to indicate all the existing app data should be deleted (the data delete function is subject to developers to implement).
For more details, please check $fh.auth API
Batch Importing Users
Multiple users can be created by using "Import Users" option. The user records should be saved in a CSV file and uploaded here.
Each line in the CSV file should be in the following format:
, , ,
Again, only the
Similar to create a new user, roles and auth policies can be assigned to the batch imported users. All the users imported in this CSV file will get the same roles and auth policies that are selected here.
During the import process, the user will be either created or updated depending on if that user has been created already. A progress bar will be appeared to show the progress of importing.
User Roles
When assinging roles for a new User or updating the list of roles a User should have, the details for each role is given below.
Customer Administrator (customeradmin)
A Customer Administrator can manage App Studio Users i.e. They can perform all the user management actions described on this page.
Domain Administrator (portaladmin)
A Domain Administrator can manage App Users through the App Admin tab. This includes actions such as creating App Users, assigning these Users to a Developers' App, and assigning App Users to a Group (for ease of App User management).
Developer Administrator (devadmin)
A Developer Administrator can do everything a developer can do, with the added ability of being able to see and access all Apps belonging to all Developers in that domain.
Analytics Role (analytics)
A User with the Analytics role can view the Reporting tab, and hence, view various reports for Apps in that domain e.g. Number of App installs or the Location distributions of App installs
Developer (dev)
A Developer can create and manage Apps. They can also preview their App and build a binary for various platforms. For some platforms, certain resources are required to build Apps, and Developers can upload and manage these resources from the App Studio.
Invitation emails
An invitation email contains a unique link, which when opened, allows a user to activate their account by inputting the password to use. The text of this email is typically something like:
Hello User,
Your account has been created and is awaiting activation.
To activate your account, please click on the link below where you can also set your password.
https://apps.feedhenry.com/studio/activate.html?t=123456789012345678901234
Regards
When creating a new user, there is an option to automatically send an invitation email. Alternatively, there is an option in the update user area to resend invitation emails.
