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. INTEGRATION GUIDE
  2. How do I integrate Biuwer into my application?

Content access security

PreviousItems to prepareNextData access security

Last updated 11 months ago

Was this helpful?

When we talk about content, we talk about the different objects that you can manage in Biuwer that can be embedded in your web application. By default, Biuwer uses a security system based on denial of access, so if you want a user to be able to consume content, you must first give them access to said content.

In the process in which a user accesses content embedded in your application, once the user is identified using an Auth Token, Biuwer verifies that that user has access to the content referenced by the Shared Resource. But how is access security configured?

In the Biuwer application, access to content is configured using the "Access Settings" option in the context menus available in Shared Spaces, Cards, Pages and Collections. Although there can be three access levels (View, Edit or Admin), the access level to configure for use through Embedded Analytics is View.

Using the Biuwer Public API, access to the content is configured using the "add_viewer" methods associated with the type and identifier of the resource to which we want to give access. See more information in .

Since the degree of customization in access to content and data can be very detailed, it is important to keep in mind that there are simple ways to grant access permissions in Shared Spaces, applying inheritance, so that access is only configured in Shared Spaces. this point (Shared Spaces), without having to customize access individually in Cards, Pages or Collections. Read more about and .

Access can be granted individually (user by user) or using groups of users. This last option, groups of users, can be used to manage access to content and data in a cleaner way, for example with groups of users that encompass end users from different clients in your application.

Automated integration
Object Permissions
Permission Inheritance
Configuration of access to content. Use inheritance for a simplified schema.