Vai al contenuto
AGORA SecureWare SA

Support

  • Home
  • Learning
  • Guides
  • FAQ
  • Video tutorial 
  • Submit a request

Getting Started

8
  • Login
  • User interface structure
  • Permissions
  • Share a resource
  • Create a Room
  • File
  • Upload a file
  • Rooms

Guide for Guest Users

9
  • Login
  • User interface structure
  • Rooms
  • Upload a file
  • File
  • Create a Room
  • Chat
  • Calendar
  • Recent activities
View Categories
  • Home
  • Learning
  • Getting Started
  • Permissions

Permissions

When a user tries to access a resource, the system will first check if for that user a permission on this resource was assigned and in case this one will be applied. Otherwise the system will check if a permission was assigned to one of the groups in which that user is member of. If any is found the greater permission will be applied. If nothing was found, in case the user is a Trust Room’s member, the system will check if a general permission for all Trust Room’s members exists: if found this last will be applied otherwise the user has no access to this resource.

Permissions levels
The available permissions levels are:

Role What you can do
Previewer See all resources on the screen + display the content of files on the screen (with a watermark)
PDF viewer Same as above + download a PDF copy of the original files (with a watermark)
Viewer Same as above + download the original files
Contributor Same as above + add content to the current resource (in case of a Room: upload files, create sub-rooms, events, …; in case of a file: upload new versions; …)
Owner Same as above + modify the settings and the permissions and delete the resource

You can also assign to a user the special permission “No access”. Since “No access” is the default permission, this level is only to be used for defining an “exception” to another permission defined (for example the file should be visible by all the group Marketing members BUT NOT by one of them).

Permissions’ inheritance
On the “Permissions settings” form for “container” resources (resources where you can store other sub-elements, like rooms and events) you can also optionally define the inheritance behavior of the defined permissions. In other words, you can define how this permission should be propagated to the new elements saved inside the current resource.

The available options are:

  • Apply (default option): this permission will be proposed by the creation of new elements, but the author will be able to change or remove it.
  • Lock: this permission will be applied also on the new elements and the author will not be able to change or remove it.
  • Don’t apply: this permission won’t be proposed by the creation of new elements. The author can however add it manually.

What are your Feelings

  • Normal
  • Sad
Share a resource

© 2025 AGORA SecureWare SA - All rights reserved.