Biuwer Docs
Biuwer.comBlogLog InTry for free
English
English
  • Welcome
  • Getting Started
    • What is Biuwer?
    • Glossary
    • How to use Biuwer?
      • Sign Up process
      • Accessing Biuwer
      • Home page and navigation
      • My user Profile
      • Managing content
      • Exploring data
      • Filtering data
      • Collaborating with data
      • The Film Rentals space
    • How Biuwer works
    • Next steps
  • Managing Data
    • Introduction
    • Data Connections
    • Datasets
    • Data Models
  • Content Management
    • Introduction
    • Personal space
    • Shared spaces
    • Favourite content
    • Pages
    • Cards
      • Data Card Editor
      • Data queries
      • KPI card
      • Vertical Table Card
      • Cross Table Card
      • Chart Card
      • Map Card
      • Custom Card
      • Calculated fields
    • Filters
    • Multilanguage
  • Creating a Dashboard
    • What questions I want to answer
    • What data sources are there
    • Setting up data connections
    • Setting up datasets
    • Setting up data models
    • Create cards
    • Create the page
    • Setting up access security
  • Security Management
    • Introduction
    • Platform permissions
    • Roles
    • Object permissions
    • Permission inheritance
    • Property of objects
    • User access logs
  • Administration
    • Organization
      • 🎨Themes
      • 🎨Color palettes
    • Users
    • Groups
    • Roles
    • Authentication tokens
  • INTEGRATION GUIDE
    • Introduction
    • Concepts to take into account
      • Contents to integrate
      • Shared resources
      • Users
      • Groups of users
      • Authentication Tokens
      • Data Policies
    • How do I integrate Biuwer into my application?
      • Items to prepare
      • Content access security
      • Data access security
      • Embedding a resource in my application
    • Integration Types
      • Manual integration
      • Automated integration
Powered by GitBook
On this page

Was this helpful?

  1. Security Management

Permission inheritance

PreviousObject permissionsNextProperty of objects

Last updated 4 years ago

Was this helpful?

Depending on whether the object has a hierarchy of child objects or not, you will have the option to "Apply same permissions to children". This is called permission inheritance, which means, for example, that object-level security settings in a shared space can be applied by selecting this option on all pages and cards contained in that space.

The permission inheritance relationship can be enabled and disabled whenever necessary:

  • It is enabled en bloc from the parent object (e.g. a shared space).

  • It is enabled or disabled individually, from the child object.

When an object has applied to itself an access configuration inherited from another object, for example, a card that inherits the security of the space it is in, the "Access Configuration" dialog will be shown as the following image.

Any changes to access settings in the space you are in, will be automatically reflected.

In cases where you need to customize permissions for an object that has the inherited permissions, simply click the "Customize Permissions" button and set users and groups of users with their "View", "Edit" or "Administer" levels. Note that in this case that object has cut off the inheritance of permissions, so any change in access settings that occurs in the space where it is, will be independent.

Inherited access settings on a page or card