JourneyApps Legacy Docs
Return to JourneyApps Docs
  • UI Components
    • button (v1) (deprecated)
    • button (v2) (deprecated)
    • capture-coordinates (legacy docs)
    • capture-file (legacy docs)
    • capture-signature (legacy docs)
    • display-file (legacy docs)
    • display-signature (legacy docs)
    • info-table (legacy docs)
    • list (legacy docs)
    • menu (deprecated)
    • object-dropdown (legacy docs)
    • object-table (v1) (deprecated)
    • object-table (v2) (deprecated)
    • scan-barcode (legacy docs)
    • single-choice-dropdown (legacy docs)
  • JS/TS APIs
    • dialog (deprecated)
    • confirmDialog (deprecated)
    • generateCSV (deprecated)
    • saveFile (deprecated)
  • Other Features
    • Access Control Rules (deprecated)
    • Global View (app.xml) (deprecated)
    • Linking Views (deprecated)
    • Sync Rules v1 (deprecated)
  • Sync Rules v2 (legacy docs)
    • Migrating to Sync Rules v2
  • Manage App Users (deprecated)
Powered by GitBook
On this page
  • Global access control rules
  • User-specific access control rules
  1. Other Features

Access Control Rules (deprecated)

PrevioussaveFile (deprecated)NextGlobal View (app.xml) (deprecated)

Last updated 2 years ago

Access Control Rules have been deprecated

Please use instead.

Data access control rules are currently only available for customers on the plan.

By default, applications in JourneyApps work on a single-tenant model, where every authenticated user has access to all data in the application. Even if the user does may not have the ability to use the application to access data, the REST APIs expose access to all data in the deployment by default.

Two types of access control roles are available: global rules and user-specific rules.

Global access control rules

These configure whether users can read or write specific models, regardless of the attributes in the model.

Example:

<!-- product_categories can be read by any user, but not modified -->
<access model="product_categories" restrict-to="read" />

User-specific access control rules

These rules restrict read or write to specific "owning" users for a model.

In this case, an explicit has-many relationship is required between the user and the objects that the user is authorized to access.

Example:

<!-- Users can only read and write their own tasks. -->
<access model="task" via="user.tasks" />
Data Rules
Enterprise