Hi all!
I am currently evaluating Fibery (among a lot of others) as a possible alternative to Confluence Cloud for my department / organization.
I am aware Fibery is a lot more than a confluence replacement, but that’s my main pain point atm.
Some Background:
We do Engineering R&D, manufacturing, and deployment of industrial products / equipment.
We also use AirTable for… a lot of things (issue tracking, service calendars, part tracking, manufacturing…) (not really looking to replace AirTable, but some synchronization would be nice)
I am looking to move us off confluence and into a wiki / knowledgebase system that is easier to integrate into our other systems and isn’t made by Atlassian.
Fibery seems to have a lot of great features and I like how active this forum is, so I hope this is somehow possible or on the roadmap.
The Hope (Document Approval, Protection, & Versioning):
We have design and process pages that need to be reviewed by a tech lead / manager and then that version associated with a particular software / hardware revision of the product.
It is actually quite strange to me this is not a front and center feature in most wiki / knowledgebase systems. I have seen it before in an instance of confluence server back in the day. Now the cloud version has removed document approvals, but you can pay extra to add it back.
I know you could just make a copy of the page every time you need a new revision and manually remove everyone’s write permission on an “approved” page with the version number in the title, but I think people who appreciate how Fibery works would understand that is a process that is sure to breakdown quickly.
This short video gives are rough idea of the type of functionality I am talking about: https://youtu.be/-dx85-k2UAs
Essentially what I need is a way to prevent anyone from accidentally or maliciously editing a versioned document, and for the reader to know that the version they are looking it has been approved or not.
I know there is a lock toggle for pages. And there is a version history, And there are permissions for Viewer vs editor, ect…
Somehow I think this must be possible through a document record, with a version field and a status, some buttons + script, combined somehow with an access template?
I have seen a lot of discussions here that seem to circle around something like this, without landing directly on it.
My brain is pretty fried though after trying this on about 6 platforms over the weekend so I will refrain from detailing everything I tried atm (most of it was nonsense) but I can add more later if it is helpful.
Thanks in advance for any ideas / insight!