I’m always a little curious when I read that someone wants to set up the exact same space twice. It often implies that there is a misunderstanding about how best to use Fibery.
If you have categories of things (Tasks, Projects, Customers, etc.) it usually doesn’t make sense to have two databases for things that are in the same category. Rather, it is logical to create a single database and then use views to ensure that the right people get to see (only) the right records in that database, i.e. people in the Engineering team see only engineering Tasks, and Finance people see only finance Tasks, even though all Tasks are in the same db.
Perhaps you want to talk about your thinking for splitting the data across two dbs.
most likely a lack of understanding as I was coming from clickup but I was thinking along the following.
I wanted to create the the basic wiki for each department, then the department heads can change the wiki to their needs including changing structures of the space itself as they see fit after the initial setup. They don’t work closely together and I would prefer not to have manage their requests.
I’m just wondering, if you are storing the wiki pages as entities in a database, why would you want to have multiple Wiki databases?
It would seem to make more sense to have a single Wiki database, and then have a Team database, and link the two.
Each Wiki entity can then be linked to a Team (or more than one if appropriate) and then each team member can access a view of Wiki entities that is filtered to only show those which are related to the Team they are in.
Interesting! That’s something I’m trying to achieve on my business setup on FIbery.
The challenge would be creating folders and views in the same structure, but changing the filters. Is it possible to create all those folders and views at once for every new team I create on Fibery
OK, I think I see where you are coming from. I setup a wiki database as the admin. Then I setup Engineering Wiki database which is linked to that, then I do the same for Legal Wiki Space and link that to the original wiki database.
So I will now have three databases instead of the original two? one for each team and one for the wiki?
BTW, I haven’t setup any teams yet, I was just giving access based on user level
Nope. Quite the contrary.
You set up a single Wiki database, and a Team database. You have a relation between them (many-to-one or many-to-many as appropriate).
Your Team database has a relation to the User database, called Members.
With a lookup in the Wiki database, you can get the linked team’s (or teams’) members.
Then you can have a hierarchical list (or more likely a smart folder) of Wiki entities, with a filter of ‘Team members contains Me’. In this way, each user who logs on only sees Wiki entities that relate to them.