I searched the forum but didn’t find an answer that fully covers this.
Current setup
We run a customer portal: the customer gets access to their Company Portal entity as a guest and sees all tickets of their company. This works well.
Because we book time on tickets but don’t want to show that to customers, we split tickets into two databases: an internal Ticket (internal communication, time booking) and a customer-facing Kundenticket, linked 1:1 through automations. That also works smoothly.
The problem
A second customer doesn’t want every user of their company to see every ticket. We need one of these:
Each guest sees only their own tickets, or
Individual tickets can be flagged as “sensitive” and are hidden from the portal.
What I tried
Filtering by “Created by” doesn’t work: it is empty for tickets submitted by guests through the form, and for tickets created by automations (e.g. email-to-ticket).
I added a People field (Sichtbar für, relation to fibery/user, multiple) and enabled “Automatically share Kundentickets with Sichtbar für” (Viewer) in the access template, and also set it in Database access. I put the guest in the field, but the guest sees “Sorry, you don’t have access”. Sharing the same ticket manually with that guest works immediately.
I considered a custom app inside the portal. Since apps run with the viewer’s permissions, filtering there would only hide data, not protect it.
Questions
Does automatic sharing via a People field work for guest users? If not, is there a recommended way to give each guest access only to their own entities?
Can individual entities be excluded from access that is propagated through a relation (like a “sensitive” flag)? Or is the only option to drop the portal and share per person?
No. The limitations for Guests include not being able to share entities automatically via a people field
Access is always ‘additive’. That is to say, if someone has access to a database, you can’t revoke that access for specific entities. You need to not share the whole database, but only share the specific records they need to see.
Thanks for the clarification with the Guest accounts.
Our other approach would be some Custom App. But I think we are also not able here to do some protecting of sensible tickets. The permissions are just the way they are if I understand that correctly. No matter how we try to look at them.
But that would mean we have to manually share single tickets. Is there an automation for that? Because we couldnt find one.
Our idea is now to use the Customer Portal as is with access to all the tickets within the Customer Company. But use a second table and Form for entering sensible tickets which just don’t “live” in the Company Portal View.
I need to check that we’re understanding each other. When you talk about ‘Customer Portal’ is this an external app which reads Fibery data, or is it a custom app running in Fibery?
The reason Guests are free is because they are limited in what they can do. If they could get access to entities automatically, it would remove a differentiator and they wouldn’t be much different that regular Members.
The limitations are not bugs or missing features, but design choices to accommodate use cases/pricing rules that suit as many people as possible
How is this decided? Is it particular departments need to see different tickets? Or are there two roles (and will always be two roles) within the portal? Manager + employer or something.
If it is two roles, you can get away with having two different relations (auto-linked) one which relates all tickets, and one which relates only the non-sensitive tickets. Then using this, you can use two different access templates. The way you set up the non-sensitive tickets is by having a formula field on the Customer Portal database which always returns False, then in the auto-linking you can check that False = Sensitive.
This should solve the issue while not changing your current workflow much, you just needed to select the proper access template when inviting your client to their portal.
BUT!
This is not flexible since it depends on a True/False boolean. If down the line you want to have different teams of your client have access to different tickets, that’s when things get more interesting (and complex, but feasible!!) I’ll explain this briefly, and if you want more info, feel free to reach out.
You can create 2 new databases:
Client Role (Linked to tickets the tickets you want that role to see)
Client Employee (Linked to Client Portal and to Client Role)
Then you can share the Client Employee entity with the person who needs access, and it will auto-link all the tickets of that client, which have that particular role tagged.
The lack of auto-sharing with guests means it’s one extra click when sharing, a bit annoying, but not so different from what you are currently doing.
Hope this helps!! If you want to run through it together, feel free to reach out and we can have a chat.
thanks for the reply and the Guest limitation. We are totally fine with that. @RonMakesSystems Thanks. We implemented your suggestion (though the other way round with isvisible = true).
I think for us it does what it should do for now,.
Thanks for all the help and infos. Much appreciated!
BR Sebastian