Overview

How do you manage access?

In Fibery, you give users and groups certain access to each App:

User or Group ---(access level)---> App

For example,

  • Mary receives Creator access to CRM.

  • Developers receive Editor access to Software Development.

By default, new Apps are visible to Admins only.

Share an App to make it visible to others:

What are the access levels?

Depending on the access level, users' powers vary:

  • Creators can

  • Editors can

    • view, create, and edit any Entity, but not configure the App,

    • create and edit Documents and Whiteboards,

    • create per-Entity Context Views.

  • Contributors can

    • view and create any Entity,

    • edit only Entities assigned to them.

  • Viewers can

    • view but not edit any Entity.

Admins are always Creators in all Apps: otherwise, it's hard to create a truly connected Workspace.

Note that users with any access to an App can see all the App Views and Entities. Access level specifies the users' ability to edit and configure stuff.

Groups

Why use Groups?

If you are on our Company plan with 20+ users in the Workspace, managing access to each App for each person individually is a nightmare. Here's where the Groups come.

Unlike most work management software, Fibery doesn't have standalone permission groups. Instead, we give extra power to existing Types that organize Users.

How to create a Group?

Entities of any Type that has a to-many relation to User Type (ex. Team, Role, Squad, Tribe, etc.) can be used as Groups. Switch a toggle on the corresponding relation to make it happen:

Group permissions implemented with a single toggle.

Once the toggle is on, Creators are free to give any Team/Squad/Tribe/... access to their Apps:

You are free to organize Users using different kinds of Groups simultaneously. The most common example is by Team and by Role (Squad + Tribe).

How to assign a User to a Group?

There is no special UI for distributing Users across Groups — simply use familiar Tables and Boards or even Users profiles:

Teams and Roles serve as permission groups.

What are default Groups?

To simplify access management, we grouped Users into two default Groups:

  • Admins always have Creator access to all Apps.

  • Everybody (includes all active Users) can have any access level.

Q&A

What if a User has access to an App via multiple Groups?

We take the maximum access level. Here is an example:

Alex is a Developer in Team Sharks.

  1. Team Sharks receives Viewer access to an App -> Alex is a Viewer.

  2. Developers receive Editor access to an App -> Alex is now an Editor.

  3. Alex receives Creator access to an App directly -> Alex is now Creator.

  4. Alex loses the individual access -> Alex is now Editor (through Developers) again.

Is there any Group inheritance (ex. Department → Group)?

Not at the moment — at least, not out of the box.

Please ping us via Intercom if that's what you are looking for. Most likely, we'll build an ad-hoc solution. Most certainly, the priority of the out-of-the-box inheritance will go up.

On a View with Types from multiple Apps, what a User will see?

The User will only see the Entities of Types that are part of the Apps they have access to.

Did this answer your question?