PERMISSION LEVELS AND ACCESS IN APPBLADE
AppBlade has three levels of access privileges.
Administrators have access to perform all functions in AppBlade for the orgs which they are assigned to over see. They have complete visibility into projects, users, and devices/mobile device management ("MDM") for their orgs and can modify as needed.
Team Members have access to manage projects to which they are assigned. They have the ability to upload/remove builds, invite users to the project, remove the project, view crash reports/feedback/session info, communicate with basic users, and perform other functions related to their projects. Team members cannot invite new users to the org as a whole, edit org users, create new teams/accounts, and control device management settings.
Basic Users have access to discover and install applications. They see AppBlade as an "App Store" and do not have additional access.
Please note that AppBlade will default to "Basic User" when adding new users, for security purposes. Also note that when adding multiple users at the same time all will be given access with the same level of privilege; You cannot bulk add users with varying permission levels.
In addition, you can further restrict access when inviting users, or when editing users, to specific projects within a Team/Account. AppBlade will default to applying privileges to this user for all projects in the team to which they are a member/to be a member:
To specify privileges for just some of the projects within a Team/Account, select the radio button for "only select projects" in the "Access to Projects" section. You will be able to pick any combination of projects from all of the projects available to that team:
If you need additional help on access and permissions, please contact us.