Flower Docs
  • OpenFlower overview
    • The "Hello World" tutorial
  • Videos
    • OpenFlower in 100 seconds
  • 🆕Setup and run
    • Cloud & Private Cloud
    • Self-hosting
      • Access local database or API
      • Google Cloud Platform
      • Heroku
      • Migration from Openblocks
      • Update MongoDB Versions
      • OpenFlower Version Update
      • Traefik loadbalancer
      • SMTP Server
    • Security
  • 🏨Workspaces & Teamwork
    • Workspaces
    • Members and Groups
    • Permissions for Resources
    • OAuth
      • KeyCloak
      • Google
      • GitHub
      • Generic OAuth Provider
    • Query library
    • OpenFlower Marketplace
  • ✨Build Applications
    • Create a new App
      • Modules
      • Version and Release Management
    • App Editor
      • Visual Components
        • Common Component Settings
        • File upload
        • Charts and graphs
        • Image
        • Option lists
        • List View
        • Drawer
        • Google Maps
        • Table
        • Messages / Toast
        • Calendar
      • Date handling
      • Bulk Editing
      • Layers
      • Data selection & Javascript
      • Use Markdown
      • Keyboard shortcuts
    • App Navigation
    • App Interaction
      • Event handlers
    • Themes & Styling
      • Design an efficient and user-friendly form
      • Customize Styles
      • Component Styling Possibilities
  • 🚀Connect your Data
    • Data source basics
    • Data sources in OpenFlower
      • APIs as Datasource
        • REST API
        • GraphQL
        • Google Sheets
      • SQL Databases
        • MySQL
        • MariaDB
        • PostgreSQL
        • Microsoft SQL Server
        • Oracle
      • NoSQL Databases
        • MongoDB
        • CouchDB
        • DynamoDB
      • InMemory Databases
        • Redis
      • File Storages
        • S3 File Storage
      • BigData & OLAP
        • Big Query
        • Snowflake
        • ClickHouse
        • Elasticsearch
      • Websocket Datasource
    • Query basics
      • Bind Query Data to Components
      • Query library
  • 🪄Workflows
    • n8n Integration
  • 💫Business Logic in Apps
    • Write JavaScript
      • JavaScript query
      • Temporary state
      • Transformers
      • Data responder
      • Built-in JS functions
  • 🙌Publish Apps
    • Share an App
    • Publish an App
    • Embedd an App
      • Embed Apps in React
      • Native embed SDK
        • Build the SDK from Source
  • 🔥OpenFlower Extension
    • Opensource Contribution
      • Develop UI components for Apps
      • Develop Data Source Plugins
    • Use third-party libraries in Apps
      • Day.js Date handling
      • Import your own JavaScript Library
    • Custom component
    • OpenFlower Open REST API
Powered by GitBook
On this page
  • 1) Application Folders
  • 2) Apps, modules, navigations
  • Anonymous User Access for Apps
  • 3) Data sources
  • 4) Query library
  1. Workspaces & Teamwork

Permissions for Resources

PreviousMembers and GroupsNextOAuth

Last updated 7 months ago

OpenFlower implements (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.

1) Application Folders

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

2) Apps, modules, navigations

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
  • Viewer

  • View and use the app, module and navigation

  • Editor

  • View and use the app, module and navigation

  • Rename

  • Edit

  • Publish

  • Duplicate

  • Export

  • Owner

  • All permissions of Editor

  • Delete the app or module

  • Set roles for members

Anonymous User Access for Apps

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.

3) Data sources

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 OpenFlower 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
  • Can use

  • Use data source when editing an app/module/navigation/library query

  • Can manage

  • Use data source when editing an app/module/navigation/library query

  • Edit data source

  • Delete data source

  • Manage data source permission roles

4) Query library

Workspace Admins and members of Developers group can create Query Library in OpenFlower and have read, write, use, and delete permissions for queries (if they can use the query's corresponding data source).

🏨
Role-based Access Control
Apps, Modules, and Navigations works the same way for permissions.
Set Permissions based on Roles for an App
Apps can be public viewable without OpenFlower Login
Overview of all Datasources of a Workspace
Set Permissions based on Roles for an Datasource