If you find any errors, typos or have general feedback, select the text and click CTRL+ALT+ENTER.

Introduction

To make Appery.io a secure place, our cloud-based platform provides a service of managing permission rights. Under account, the following roles for all the users on the team can be set:

  • Admin
  • Team Lead
  • Developer
  • Tester

Within a team, view/edit/delete permissions to the following resources can be configured:

General team building information

Only Appery.io users with Trial, Pro, Team or Enterprise plan can initiate building a team to share their resources/items. When invited, users must join your team (and they must be existing Appery.io users).

Every team user has his/her particular permissions to resources/items within a team. Оnly Admins and Team Leads can manage team roles and enable/disable resources/items for their team:

While managing permissions for a particular team user, click the arrow next to Save to get to the drop-down menu with the following options:

  • To enable/disable all the resources/items for a particular user, select Select all/Deselect all.
  • To remove a user, select Remove. If you decide to remove the user from your team, you will also have to confirm your choice in the confirmation popup. The removed user’s plan will be changed to Trial by default.
  • Select Save & notify to keep the changes made and notify the user that his permissions have been changed. Upon clicking Save no notification will be sent.

Generally, there are three cases when a team member can get notifications: invitation to the project, changing  particular permissions (Save & notify option selected), and removal from the project.

Any team user (except Tester) who creates a new project has custom full permissions to it (viewing, editing, deleting), which may be later disabled by Admins/Team Leads.

Inviting users

To invite new users, obtain seats first. Additional user seats are available within an active Trial, Pro, Team or Enterprise plan. User seats can be shared with Trial plan users only. If a user has a plan other than Trial, he/she needs to switch/downgrade to Trial.

See our pricing for user seats.

To add user seats, go to Account > Plan, click Change plan. Enter number of user seats, fill in billing information, click Continue.

Then, to invite a user, switch to the Team tab and enter his/her email. Click Add user:

If you have a Trial account and you invite a user with a Trial account, your accounts will be merged and the nearest trial expiration date will be chosen. So you may expect shortening of your trial period in case your teammate has an older trial subscription.

You may also invite inactive users (those with the expired trial period (or suspended plan payment)). If such users leave your team, they become inactive again (unless they purchase a paid plan (or renew their suspended plan payment)).

After a user gets a confirmation email, he/she should complete the registration process. Before that, Admin can see a pending notification under Team tab:Pending

A user can belong to ONLY one team and have ONLY one role within the team.

Joining a team

Open your Account tab to see an invitation. You can either join team or decline the invitation.

After clicking Join team, you would get the warning notifying of the changes to be made to your account:

  • all previously created resources will be transferred to the team owner.
  • if one leaves the team, all the resources he/she has created in the team will be transferred to the team owner.

If you have a Trial account and you accept an invitation from a user with a Trial account, your accounts will be merged and the nearest trial expiration date will be chosen. So you may expect shortening of your trial period in case your teammate has an older trial subscription.

Click Join team or Cancel to join later. After a user joins the team, the Admin is notified.

Any user joining the team gets Developer‘s role by default. This role may be changed to Team Lead, Tester, or Admin. New users can see the shared plan, its owner and the team under their Account > Plan tab:

No resources can be enabled for the users who haven’t joined.

If a user joining the team has resources/items named identically to the name of the resources/items already existing within the team, to avoid conflicting names, an underscore (_) will be automatically added.

Leaving a team

To leave the team, go to Plan tab under Account, click Leave team and then confirm.

When team users are removed seats are returned to the owner.

User roles and permissions

The default permissions for each role are listed below.

Role
Resource
Admin Team Lead Developer Tester
Apps
  • All permissions and resources are enabled by default.
  • Admin permissions are not editable and can’t be changed even by another Admin.
  • All permissions and resources are enabled by default.
  • Particular resource can’t be disabled.
  • Particular permissions to items can be modified by Admin or another Team Lead.
  • All resources are disabled by default.
  • Edit and View permissions are enabled by default for enabled resources.
  • Can create new items even if resource is disabled.
  • Particular permissions to self-created items can be modified by Team Lead or Admin.
  • All resources are disabled by default.
  • View permissions are enabled by default for enabled resources.
  • Can’t create new items (except of creating and saving database collections and rows).
Database
Server Code
Proxy
Plugins
Certificates
Webhooks
API Express
Support Packs Admin can purchase a Support Pack. white-no-symbol-small white-no-symbol-small white-no-symbol-small
Billing Admin can add seats and change plan. white-no-symbol-small white-no-symbol-small white-no-symbol-small
Team Management
  • Can manage team (invite users, change roles, configure permissions and resources).
  • Can be removed from the team or downgraded only by another Admin.
  • Can be removed only if there is another Admin in the team.
  • Can manage team (invite users, change roles, configure permissions and resources).
  • Can be removed from the team or downgraded by another Team Lead or Admin.
white-no-symbol-small white-no-symbol-small

Admin role

Only Admins can edit billing information, buy support packs and have full access to all the facilities within the project (creating, viewing, editing, and deleting resources/items).

There can be more than one Admin on the team; if so, any of them can manage the subscription and billing information. Only Adminscan access Plan, Profile, Team, Support Packs, Billing, Invoices, and Social Sign In tabs. The rest of the team have access to Plan, Profile, Team, and Social Sign In tabs only.

Under Account tab, Admins can view information on their plan, role, subscription and next billing date in Plan tab. Also, promo codes generated by Appery.io can be entered here to get discounts for some of its services. Changing/canceling plan or leaving team is accessible from this tab as well:

Admins can remove Team Leads/other Admins from the team. But Admins can’t remove their own account until a new Admin is assigned to the project.

Under the Team tab, the team roles can be managed and certain resources/items enabled/disabled, existing users may be removed and new users invited. If successful, such updates will be notified of.

Admins can’t disable their own permissions, as well as Team Leads‘ permissions.

Team Lead role

Team Leads manage the overall team workflow, but not its subscription. They can’t buy support packs either.

Delete permissions are enabled for Team Leads as well as for Admins, by default. Like Admins, Team Leads can remove users and enable/disable resources/items for a particular user for a particular item or delete them.

Team Leads can also change roles for Developers and Testers.

Team Leads can manage permissions for Developers and Testers and remove them from the team, but can’t set/manage any permissions for Admins and Team Leads (including themselves).

They still can switch/downgrade team users (except Admins) to any role or remove them (including other Team Leads).

Team Leads can downgrade to Developers or Testers, but will be unable to revert this migration later.

Developer role

Developers can’t manage the subscription and billing information, change the roles of existing or invite new users.

Developer‘s only default permissions are viewing and editing shared resources; deleting items isn’t allowed.

Permissions to any resource/item (including creating and deleting them) can be enabled/disabled for a Developer by Admins/Team Leads from Permissions tabs under Apps, Databases, Serever Code, Secure proxy, Plugins, or Resources.

If some resource/item is disabled for a Developer, he/she can still create new items in this category with custom full access to them.

Tester role

By default, Testers may only view (“read only”) the resources/items enabled by Admins/Team Leads. The options like Rename, Delete, Backup etc. are inactive. They can’t create new items on the project either.

In the builder, when making any changes to any of the items and trying to save them Testers will get a message:

Such message also appears when some changes have been done to subscription plans by Admins.

Edit and/or Delete permissions to a particular resource/item can be enabled for Testers by Admins/Team Leads from corresponding Permissions tabs. A Tester can then make any changes to this particular resource/item, except creating new ones. However, creating (and saving) collections for a particular database can be enabled by Admins/Team Leads under Databases tab.

Managing particular permissions

Appery.io provides enabling/disabling permissions to particular resources/items for particular user(s).

The following example shows how app’s default permissions are modified by Admins/Team Leads.

Enabling/disabling permissions to one of the apps you DON’T modify any permissions to any other app or resource/item.

Example

To enable/disable permissions to the particular application, go to the Apps tab. From the apps list, choose the app and, under Permissions tab, enter the mail of the user, then click Add:JillRobertsInvited

The invited user will be listed below and notified. If the user is already on the list, a message This project is already shared with user jill_roberts@mail.com will appear.

In the screen below, the first listed user – Dan Brown (Team Lead), has full access to NewApp application, the second user – Steve Scott is given only View and Edit permissions according to his Developer role, and the third user on the list – Ann Smith (Tester), can only view the app:

Admins can disable the default Team Leads‘/Developers‘/Testers‘ permissions to view/edit and/or delete some particular app. To do it, start with Delete option, then one is able to check Edit and View boxes.

Permissions to all the other resources may still be enabled for this user. For example, Dan Brown (Team Lead) has default full permissions to the other applications (except NewApp).

To cancel this revoke and reenable full access to the app, check the Delete option first, only then check View and Edit boxes, respectively. This succession applies to all the changes made within the shared resources/items.

Team Leads can disable any permissions within this app for Developers and/or Testers or enable new ones.

Similarly, Admins/Team Leads can modify permissions to a particular resource/item for a particular team user from under the corresponding Permissions tabs under Databases, Server Code, Secure Proxy, API Express, Plugins, or Resources.

Team collaboration

The main purpose of team collaboration it is to provide the ability to have several users working on one application/item at the same time.

Example

Two different users (Dan Brown and Steve Scott) are looking through the same shared app:

Notice the notification panel at the top:

The first field shows how many users are watching the same app. With only one user (Dan Brown, for example) watching the app, the number of active users equals 1:

Now, Steve Scott is connected. The active users now equal 2:

Click to see who is watching the app:

When Dan Brown opens the startScreen page, the owner receives the notification, Steve Scott joined this resource (startScreen):

Steve Scott adds a component to the startScreen. Dan Brown receives the notification, Steve Scott is working with this resource (startScreen):

Dan Brown won’t see the majority of the changes until Steve Scott clicks Save. However, when one user creates or deletes pages in the app, the other sees a notification:

When Steve Scott clicks Save, Dan Brown receives another notification: Steve Scott saved the project and information on the name of the saved resource and the time the changes were made:

To view the changes, Dan Brown should reload the page. To do this, Dan Brown should reload the app in the builder, or click Reload app from the notification list.

Now, Dan Brown can see all the changes performed by Steve Scott.

When Steve Scott closes the startScreen, Dan Brown receives the notification, Steve Scott left this resource (startScreen):

If Dan Brown and Steve Scott place components on the same area of the screen, 4 actions become available:
Override

  1. If Dan Brown clicks Cancel, nothing happens; the popup will simply close.
  2. If Dan Brown clicks Reload app the app will simply reload (first changes will be applied).
  3. If Dan Brown clicks Save non-conflict resources the following will occur: if Dan Brown and Steve Scott have added the same components, then the component will be used (e.g. Dan Brown added a button and Steve Scott did the same. A button will be used). If they are not the same, only the first changes will be saved.
  4. If Dan Brown clicks Override, only his/her changes will be saved.