Has something changed with form permissions?
Since this morning, no user can create entities using forms.
They seem to be only available to people with Creator access at the Space level.
The default form is also not working.
Where are these views located?
What permissions have you granted the ‘Basic user’?
I moved them all into the default workspace at the root of the structure.
They were under each space individually.
At neither location do they work.
Users have Viewer access on all Spaces.
On the databases, users have Editor access.
This has not changed since yesterday, but now nobody can use the forms.
The only way for users to be able to use forms is if I give them Creator access on the Space. Editor access or below does not work.
Giving them Creator access on the Database also does not work.
If the views are in the default space, what do you mean when you say that you give them Creator access on the Space?
When I moved it, I assumed that since it was in the root of the structure, that was the cause of the issue. So I moved it back. But that did nothing.
Users can see the containing Folder. The Folder is empty.
Where are the form views now? Which space? What access does the basic user have to that space?
Perhaps you can share a screenshot of the sidebar
Administrator view
User view (I have hidden the Profiles Space)
Before the forms were at the top level of their respective Spaces. Moving them back, they’re still invisible to users.
Administrator view
User view
Spaces privileges
Database privileges
The test user is in the Support team.
As I said, only after setting the Space access to Creator does the form appear again
The AI is absolute dogwater. It suggests the reason people can’t see the forms is because the entities are associated with another entity that they don’t have view privileges on.
If that were the case, why is it only happening now? And forms don’t have an associated entity—it hasn’t been created yet!
Another example
Admin view
Marketing user view
The Marketing employee no longer has access to Compose Emails, New Posts, and New Campaigns… That’s their entire workflow gone!
Hmm, Ok, it seems like we might have unwittingly broken something. Will update here when it’s fixed.
Sorry for the hassle.
Fixed. Sorry for troubles, we are slowly rolling new permission model and it caused this problem.
I really don’t mean to be a dick, but can you guys please work on your QA before rolling new things out? For a large organisation depending on Fibery, working exclusively with forms, (like one that I am supporting) it means they had to stop work for 10 hours.
This was an 10 hour outage, and I hope internally it is being treated as such, with additional measures being added to prevent something like this from happening again.
Luckily it was during the night, so realistically it was only 3 hours, but still not ideal, and preventable.
If it’s a one time things I understand, but I’ve been seeing it happen more and more, features being rolled out either without enough testing, or without enough thought.
I like shiny new things just as much as the next person, but not if they are easily breakable / useless / break other shiny things…
Just my thoughts.
You are absolutely right. This bug was slipped since prod was updated routinely with a parallel running permission model that should not break anything, but apparently there was a typo that causes troubles.
All such incidents internally have post-mortem documents with actions.
2 Likes
Okay thank you for your response, I am glad it is taken seriously! And was able to be fixed quickly. Thanks again!