Good evening everyone. Having spent time getting familiar with Infinity and its capabilities, I was starting to think about how I might practically organize content in the tool. As I was doing so, I tried to visualize a hierarchy the provides separation of data, with appropriate permissions for the content. In my search for strategies I stumbled upon this thread. I think it deals with some of the challenges I am facing. Like others have commented, it seems like folder permissions are important.
However, given that this seems like an overall lower priority for implementation, I figured that I must be missing something. Clearly, the Infinity team has a vision for how the product would be used and why the current permission scheme supports that approach. So I looked at Infinity videos and tutorials for clues on how they think about organizing content in the tool.
However, I’m struggling with how the current permission model enables what they propose. For instance, they suggest organizing a workspace by department (using a company as the Workspace). In one video, there is an example of adding an HR department as a board. If the intent is to keep basic employee data in this board, available only to HR staff, then this might work. However, if I wish to also include additional content, such as an Employee Onboarding section, the model instantly breaks. I can’t provide employees access to the onboarding information without also providing them access to employee data, as the most granular permissions are for a board. That means, I’d need to create another board for the onboarding information? Is that the expectation?
I worry that this quickly turns into a very shallow hierarchy with either lots of workspaces or lots of boards. Then the concept of a neat and well contained board per department disappears. Again, maybe I am not looking at this problem correctly, so suggestions are certainly appreciated.
I also expect that whatever structure I define may evolve over time, but in thinking this through I realized that a feature is missing to make that happen.
I can move boards between workspaces, but there is no way to move a folder between boards. Here is an example of why this is important. Imagine that I create an amazing set of data in a board that I want to share. I can’t provide everyone access to my board as there is other data I don’t want to share. I could create a new board for this data and move it there, but there is no option to move folders to a new board.
I could duplicate the board, delete all of the data that I don’t want to share and have a new board with this folder (or set of folders). But, there isn’t a way to consolidate these boards. Imagine I and others need to do this. I might find that we could consolidate these to create a new board with common content. As it is, I end up with lots of boards with very few folders and a mess at the workspace level.
Hopefully this makes sense and the challenges I am facing are just oversights on my part. I am just not seeing a way to do these things with the product that exists today.