Content access security
Last updated
Last updated
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 Automated integration.
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 Object Permissions and Permission Inheritance.
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.
