Enable Button Click/Execution for GUEST Members

Ideas & Features
1

Hi Fibery Team,

First off, I’d like to say that the “Automatically Share Entities with Assignees” feature is fantastic. It’s a game-changer for collaborating with guest users on specific tasks.

However, I’ve encountered a limitation that I hope can be addressed. When an entity is shared with a user who is a GUEST, even if they have the highest permissions within that entity, the action buttons are disabled for them. This restriction prevents guests from executing crucial actions, hindering our collaborative efforts.

Use Cases Where Enabling Buttons for Guests Would Be Beneficial:

  1. External Collaborators Completing Tasks:

    • We work with freelancers and consultants who are granted guest access to specific tasks or projects. Allowing them to click a “Mark as Complete” button would streamline project management without needing to upgrade their access level.

  2. Client Approvals:

    • Involving clients in the approval process is essential for us. Enabling a “Approve Design” button for guest users would make it easier for clients to provide timely feedback directly within Fibery.

Enabling button execution for GUEST members would significantly enhance the flexibility and utility of Fibery for teams that rely on external collaboration. It would allow us to maintain appropriate access levels while still leveraging the powerful automation capabilities that buttons provide.

2

Guests are free because they are read-only. We do want to add Collaborators (similar to guests, but with editing rights), however we did not finalize the conceptual solution. One idea is to allow 2-3 collaborators for every paid user, for example. But it will be done after more important permissions features, like database access, re-do access to People database, etc.

2 Likes
3

I would love this as well. More generally: making buttons accessible on read-only databases. Example: a button that creates a relation in a database which I have access to will not work if the entity i have access to is read only. Think about things like: “Use this template” (where template is read-only)

Maybe an option in the buttons to allow on read only?

I understand that you don’t want to allow guests to do much in order to get them to a paid plan, but this is also relevant for paid users who only get read-only access.

Looking forward to all the coming permissions features!!

4

Technically it is very hard to implement, since buttons are executing under logged user and permissions are applied accordingly. So we will have to somehow overcome this and it may create loopholes for weird things.

5

I see… makes sense! Thanks for the explanation