AppInvento Backend Builder Guide
  • 👋Welcome to Our Product - AppInvento
  • Overview
    • 💡What we do
    • ✨Our Features
  • Product Guides
    • 📽️Create your first project
    • 🎇Create new Role
    • 🌾Create new collection
    • 🎄Create a new collection field
      • String Data Type
      • Float Data Type
      • Integer Data Type
      • Enum Data Type
      • Reference Data Type
      • Date Data type
      • Boolean Data type
      • Geo Data Type
      • File Data type
      • Virtual Data type
      • Embed Data type
      • Map Data Type
      • Mixed Data Type
      • Buffer Data Type
      • Decimal128 Data Type
      • Email Field
      • Email Verified Field
      • CreatedAt field
      • UpdatedAt Field
      • CreatedBy Field
      • UpdatedBy Field
      • isDeleted Field
      • Deleted_at Field
      • Deleted_by Field
    • 🔐Set Access Permissions
    • 💪Commit Your Changes
    • 🧑Inviting Members
    • 🔗Routes
  • Fundamentals
    • 🛠️Getting set up
    • 📝Setting permissions
  • Use Cases
    • 🎨For Designers
    • 🖥️For Developers
Powered by GitBook
On this page
  • Set Collection Permissions​
  • Set Field Permissions​
  1. Product Guides

Set Access Permissions

This page empowers you to fine-tune the access permissions for different roles within your project, allowing for precise control over user privileges and functionalities.

PreviousDeleted_by FieldNextCommit Your Changes

Last updated 1 year ago

In order to allow users to access the entity, we need to set its permissions.

Permissions can be controlled separately for each of the following actions:

  • Create

  • Update

  • Get

  • List

  • Paginate

  • Remove

These actions can be set to one of the following:

  • Public - No authentication is necessary, granting access to all users, regardless of their assigned roles.

  • All Roles - All roles have the capability to perform the action without any restrictions.

  • Granular - Only specific roles that have been designated can carry out the action, providing a more fine-tuned level of control over access permissions.

Set Collection Permissions

By default, all of the actions are set as All Roles.

In this example, some of the actions have been changed to Public, while the others remain as All Roles.

In the following example, we use the Granular setting to fine-tune the permissions for a role.

  1. To access the permission settings for a specific collection, navigate to the Overview page and choose either the Create Collections option or select Collections from the left menu.

  2. Locate the desired collection and click on it, From there click on the Set Permissions. This opens the permission settings.

  3. By default, all actions including Create, Update, Get, List, Paginate, and Remove are initially set to be accessible by All Roles.

  4. Fine-tune permissions by changing the Delete permissions from All Roles to Granular and then select from the displayed roles the Admin role. This ensures that only users with the Admin role can delete projects.

Next, we will proceed to establish permissions at the field level.

To add field-level permissions in the Update action, simply click the downward arrow, then select + Add Field. From the provided drop-down list, choose the specific fields for which you wish to grant access to updates.

Click on the Save button to save your changes.

Set Field Permissions

🔐
​
​