Skip to main content
Question

What is your policy for creator rights/interface rights? How do you manage frustration?

  • April 22, 2026
  • 0 replies
  • 10 views

Hugo Riviere
Forum|alt.badge.img+3

Hi,

I have around 50 users distributed in 20 roles and we are 2 creators.

So far, my policy to manage rights is :
- Open base for dashboards: creator rights for managers on read-only base containing only synced tables
- Interfaces dedicated to every role: every operational role has dedicated interface with editor rights (with viewable/editable fields adapted to their function in the workflow)

Drawback of this is:
- users can’t share links to other teams from their interface since other roles don’t have access to them
- managers feel they are hidden some information and regularly ask for access to other role interfaces
- managers feel they could have improvements ideas for their interfaces by browsing through other team interfaces

In the long term, my perception is that granting rights when asked is a way to:
- miss evolution of workflows/new needs for information
- degrade user experience and efficiency since they will multiply click through other interface for a specific information

So I mostly question the access demands, rather than granting them. This creates feelings of frustration, inertia and silo effect.

Have you met such situation?
Do you feel I should open rights? or I should stick to my policy but educate more about it?
How would you educate managers to those long-term stakes vs short-term needs?