Permissions for Resources
Last updated
Last updated
© Lowcoder Software LTD
Lowcoder implements Role-based Access Control (RBAC) by assigning a set of permissions to different roles. These permissions determine the actions users can take on resources, including apps, modules, navigations, folders, query library, and data sources.
Only workspace admins and members of Developers group are allowed to create resources. Workspace admins are in fact the owner of all resources.
Folders help you sort out the Apps, Modules, and Navigations in your Workspace. Only workspace Admins and members of Developers group have the following permissions for folders:
Create
Rename
Delete
Move Apps, Modules and Navigations into or out of folders
The way permissions are applicable for Apps, Modules, and Navigations are the same.
The owners of an App, a Module, or a Navigation can add members and assign different roles to them. To set Permissions for Users or Usergroups use the Share button in the App Editor at the top right, then click Add members.
Choose members and / or groups from the list and set roles for them.
The available roles and their corresponding permissions are listed in the table below.
Role | Permissions |
---|---|
|
|
|
|
|
|
If you want to make an app or a module or a navigation public to all users (including anonymous users), you can toggle on Make the app public in Share settings.
Only workspace admins and developers can view the Data Sources page and create new data sources.
For each data source, workspace admins and the creator can change its Access Control. Go to Lowcoder homepage > Data Sources, and click ···
> Access Control.
In Access Control settings, add members or groups from the workspace, and then choose their roles (Can use or Can manage).
The permissions of these two roles are listed in the following table:
Role | Permissions |
---|---|
|
|
|
|
Workspace Admins and members of Developers group can create Query Library in Lowcoder and have read, write, use, and delete permissions for queries (if they can use the query's corresponding data source).