I am new to Laserfiche admin/development and have a question about how Teams, Projects, and Repositories are connected. In my organization, we have segmented several repositories by department, so for example the HR repository and the Ops repository. But when it comes to building processes and forms for each department, we are currently just using the "Global" team/project. It seems as though this could rapidly become unwieldy. I think we should try using the Teams and Projects feature as well. So, for example, creating the "HR" Team and then a Project for specific tasks we want to build out. (I think we could also then use the HR Team to manage user permissions for people in the actual HR department who will use the processes we've built for them). What's unclear to me is the relationship between the Teams/Projects and the Repositories. Will the Teams/Projects we build be able to move content into any of the Repositories we select as part of the process, or is there somewhere that directly links Teams/Projects to Repositories? Or am I not understanding how things are organized conceptually, etc.? Thanks for any direction and assistance!
Question
Question
Replies
This answers post by Tesia Au discusses best practices for Teams and Projects and is worth reviewing. The Cloud documentation is another good resource for learning about Teams and Projects. I would also encourage just trying things out with a test process. This has been made easier with the ability to migrate between Global and team contexts described here.
In regard to your question about whether Teams/Projects are able to move content into any of the Repositories selected, the answer is yes. Processes interact with Repositories using the ProcessAutomationUser. As long as you grant appropriate Repository access, entry access rights, feature rights, and privileges to this user, your processes should have no issues interacting with a specified repository.