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
  • Choose your restricted setting
  • Restrict Data by Fields with Username

Was this helpful?

  1. Bloc Editor
  2. Bloc Settings

User Restricted Data Settings

PreviousData Display SettingsNextManage and Build Templates

Last updated 1 month ago

Was this helpful?

The User Restricted Data Settings are a series of settings that are solely based on what data the user can see. These settings can be used to prevent individuals seeing each others data. These settings are independant from the settings.

Choose your restricted setting

These are the settings to decide which data gets loaded for the logged in user.

No Restrictions

All data will be loaded regardless of who entered them.

Only Load Logged In Users Data

This will force only the users data to appear, nobody else's.

Hide Totally except for person with permission "Can See Hidden Data"

Hide locally but available in other forms

Hide from person submitting data, unless specifically shared with them

Hide from person submitting data, unless specifically shared with them, but allow in dropdown

As these options are growing and becoming more complex we are working on a new and improved add/remove data restrictions feature to replace this.

Restrict Data by Fields with Username

It is possible to use data inside the fields to also determine who sees what data. This is useful for creating data on behalf of other people or for someone with one role in an organisation to be managing things for others.

In the images below, you will see a bloc where this option has been set to two fields, User Example and Field 1. What this means is, any entries where these fields contain the username of an individual, that individual will be able to only that data. In the example below, the user with the username sampleuser can only see data where User Example or Field has a value called sampleuser.

It is important to note, a person with the will always be able to see all data.

You can also configure this . This is currently a "hidden feature" and requires contact with to support@blocworx.com for implementation. It also requires the setting below: Hide from Person submitting data, unless specifically shared with them.

No data gets seen by anybody (even the user's own data), except for people with either the or the .

Data does not appear in the bloc where the data has been submitted, but is available in dropdowns, fields and rules that are connecting to this data. For example, a field like might still need this data even if we don't want it shown on this bloc.

This option prevents data from being seen by anyone, unless it has been shared with them using our hidden feature: .

A slight variation of the option above, with this selected, the above applies but if there id a file like using this data, then it is available unrestricted.

This can be used in conjuction with the fields available in so that there are more useful ways to populate the user data into a field.

Dropdown from another bloc
Dropdown from another Bloc
User Based Components
Bloc, User and Role Access
so data can be shared amongst users or shared amongst roles
Share Restricted Data with Other Specific Users
Admin permission
Admin Permission
Can See Hidden Data permission
The two fields we have selected that might hold the username.
The data output for the user that has the username sampleuser.
An admin can see all data and even create data for others, in this case adriandecleir created the top entry where Field 1 had a value "sampleuser"