Blocworx Documentation
  • Welcome to Blocworx
  • The structure of Blocworx
    • What is a project?
  • Getting Started
  • How To's
    • How To's
      • Get Started: Build a Simple Module
      • Build a simple invoicing system
  • Page
    • Page Overview
      • Page Sections
      • Modules in Pages
      • Sub Pages
      • URL Links
    • Edit a Page
    • Manage Pages
  • Module
    • Module Overview
      • Module Sections
      • Blocs in Modules
      • Automated Reports
    • Module Editor
      • Add, remove and move Sections and Blocs
      • Edit Module Location & Icon
      • Edit Module Details
      • Import from another Module
      • Delete a Module
      • Make this module available to child instances
    • Manage Modules
  • Bloc
    • Bloc Overview
    • Bloc Front End Overview
      • Data Display
      • Advanced Reports
    • Bloc Editor Overview
    • Pdf & Doc File Template Builder
    • The Blocworx Process Flow
    • Edit Templates
  • Bloc Editor
    • Bloc Form Builder Preview
    • Fields, Tools and Charts
      • Standard Input Fields
        • QR Code
        • Text
        • Large Text Field
        • Checkbox
        • Multi Button
        • Dropdown from List
        • Date/Time Selector
        • Bluetooth (Beta)
        • Button
      • File & Image Fields
        • File Field
        • Multi File Field
        • Image URL Field
      • Linked Data Selection Fields
        • Dropdown from Bloc
        • Autocomplete
        • Radio Buttons From Bloc
        • Checkboxes From Bloc
        • Link Data Field
      • Content Editing Components
        • HTML Field
        • Separator Field
        • Content Editor For User (WYSIWYG)
        • Content Editor (WYSIWYG)
      • User Based Components
        • Create User Pop Up
        • Logged in Users Information
        • User Select Field
        • Signature & Authentication
      • Dynamic Output & Variable Components
        • Time/Date Difference
        • Auto Generate Field
        • Plain Data Field
        • Maths Field
        • Field Merge Builder
        • Label Field
        • Barcode Generator
      • Third Party Integration Components
        • Blocworx Gateway
        • Bartender Integration
        • File Builder
        • Mindee API
      • Charts, Results & Data Feeds
        • Local Data Doughnut Chart
        • Advanced Chart Set 1
        • Results Box
      • Sub Blocs, Tools & Components
        • Submit Button
        • Sub Bloc
        • Cross-Bloc Data Manipulator
        • Bloc List
        • Mail Alert
        • Calendar & Resource Planning
    • Field Create, Edit, Parameters, Rules and Actions
      • Creating a Field
      • Editing a Field
      • Field Parameters
        • Choose hidden options for this field
        • Mobile Configurations
        • Rule and Actions Based Parameters
        • Main Field Parameters
        • Conditional Value
        • Set Character View Limit
        • Conditional Visibility
        • Dynamic Data Update (Update Value Based On Another Date Field)
        • Field Names in Different Languages
        • Manage Field Actions
        • Load Data from Another Bloc
      • Field Rules and Actions
        • Can not be empty
        • Must Be Equal To
        • Cannot Be Equal To
        • Must be Between Two Values
        • Must be at least X number of characters
        • Must be exactly X number of characters
        • Item must have been entered elsewhere
        • Item must not have been entered elsewhere
        • A specific value is required elsewhere
        • A specific value cannot be present elsewhere
        • Populate another local field with data from elsewhere
        • Populate another local field with total from elsewhere
        • Max Allowed Duplicates
        • Can only be numbers/integers
        • Keep Data for Next Entry
        • Must be Certain Format
        • Cannot be Equal Another Local Field
        • Must be equal to another local field
        • Populate another local field with part of this field
        • Populate local field with data from another local field
        • Must have matching equivalent data in another form
    • Bloc Settings
      • Main Bloc Settings
      • Functional Behaviour Settings
      • Bloc Layout and Visibility Settings
      • Data Display Settings
      • User Restricted Data Settings
      • Manage and Build Templates
      • Bloc, User and Role Access
      • List of available Field Slugs
      • Manage Bloc Scheduler
  • Manage Data
    • Manage Data Overview
    • Raw Data and Counting Reports
    • Look Up/Edit Data
    • Find and Replace Data
  • Administration
    • Admin & Development Overview
    • Manage Users
      • Profile Filter
    • Roles & Permissions
      • Roles
      • Permissions
    • Manage Mail Alerts
  • App Settings
    • Sign In With Google
    • Timeout Setting
  • No Code Development
    • Manage Blocworx Instances
      • Parent and Child Instances
    • Edit Theme
    • Manage Modules
    • Manage Pages
    • Extra and Beta Features
Powered by GitBook
On this page
  • Admin: Full Administration and No Code Development
  • Can Access the Admin Landing Page
  • Can Manage Users/Profiles
  • Manage User Roles
  • Can Change Roles and permissions of users
  • Can Access the Data Look Up/Edit Page
  • Can Access the Alerts Page
  • Is not included in data restrictions set on Blocs.
  • Raw Data and Count Reports
  • Can Edit Data inside a Bloc
  • Can Can See Hidden Data
  • Can Submit Data even when Submit Data option Is disabled
  • Can still see blocs that are visually removed from the list.
  • Can See Export All Data Button in Bloc
  • Can unlock Filtered Fields

Was this helpful?

  1. Administration
  2. Roles & Permissions

Permissions

PreviousRolesNextManage Mail Alerts

Last updated 3 years ago

Was this helpful?

Admin: Full Administration and No Code Development

This is the most powerful permission that exists. It has unlimited access to every page, it automatically has every permission and you can even build or delete blocs and modules with this permission. There is no higher level in a and the only other one that exists is users that have the same access except over multiples instances with the same user.

Can Access the Admin Landing Page

This permission is designed to give someone access to the Admin and Development page, but without yet committing to giving them access to pages within it. You would use this as a way to control an admin who can do certain things, for example, if you want a person to be able to add Mail Alerts but cannot add users, you would give them this permission along with the "Can Access the Alerts Page" (See below).

It is the permission that allows this link to appear in the sidebar:

Can Manage Users/Profiles

This is a typical Administration permission. With this permission they can add, edit and delete users. They can also add roles to a user.

Please note: This permission is not enough for them to add permissions, change roles of users or create new roles. The reason for this is that we consider the ability to add permissions directly or create roles (that can then be added to users) a very high level permission. With this in place, a user who can simply add other users but they do not have the ability to create a user with Full Admin/No Code Development access. This restriction is useful for admins who you do not want to give too much access or responsibility to.

To Access this page, they also need access to the Admin Landing page using the "Can Access the Admin Landing Page" permission.

Manage User Roles

This permission allows someone to add/remove roles from a user. This obviously only applies to users who have the above role "Can Manage Users/Profiles".

Can Change Roles and permissions of users

This is a powerful permission. Somebody with this permissions can create new roles (with any permissions they want in those roles) or can simply add the most powerful of permissions to a user. This is for high access level admins.

Can Access the Data Look Up/Edit Page

Note: They cannot edit data with this permission, so they can only use the Look Up/Edit Data page for looking up records. They need the "Can Edit Data inside a Bloc" to be able to edit data.

Can Access the Alerts Page

To Access this page, they also need access to the Admin Landing page using the "Can Access the Admin Landing Page" permission.

Is not included in data restrictions set on Blocs.

When a user has this permission they can see all data in a bloc regardless of the various restrictions that may have been put in place. Restrictions might include the following:

Please be advised this is a powerful role in terms of what data an individual can see..

Raw Data and Count Reports

Can Edit Data inside a Bloc

Can Can See Hidden Data

It's currently possible to hide data entirely from users inside a bloc. This permission makes an exception to this rule by allowing anyone with this role to see this data.

Can Submit Data even when Submit Data option Is disabled

Can still see blocs that are visually removed from the list.

This permission is designed to override this feature, it is mainly for admins who still need to see the bloc in the module even if other users cannot see it.

Can See Export All Data Button in Bloc

Can unlock Filtered Fields

This option forces users to only see data filtered based on the value of a field that is set (for example a company name). They may have no control over changing this, thus you can prevent other data from being seen by forcing a "lock" on this filter.

This permission overrides this lock and allows the user to continue to change the filters in the bloc.

This roles gives a user access to the Found in .

This permission allows a user to create .

This permission allows users access to the section.

This allows users to edit data inside a bloc and edit data in the .

Please note, even without this role its possible to allow users to edit data in specific blocs with the bloc setting: . This may be preferable for limited editing.

It's currently possible to disable the ability to Submit Data in a bloc using the Bloc Setting: . This completely prevents user submissions. However a user with this permission can continue to submit data. This is useful in blocs where some users only use it for looking up data but others are allowed to create new records.

It is currently possible to remove the visibility of blocs from a list of blocs in a module. This is different to completely preventing access to the bloc. It is a non-secure way of tidying up the look and layout of your without preventing real access if they had the link. The user may still need to see this bloc as a , or you may want to create a separate . This removal process can be done using .

It is currently possible to hide the Export All Data button in a bloc by using the bloc setting . This permission overrides this.

It is currently possible to lock in filtering that occurs as a result of the parameter. This can be done by clicking the option : .

Data Look Up/Edit Page
Manage Data
Mail Alerts
Profile Filtering
Data Lookup/Edit Page
Raw Data and Count Reports
single instance
module
Sub Bloc
link to this bloc
this bloc setting
Anybody can edit data in this bloc
Cannot Submit Data
Force data filter fields for those without permission
Specific User Restricted Data Settings
User Restricted Settings by field values with usernames
Data Filtering Field
Hide Export All Data Button