When setting up the Platform System, the Administrator should determine how the organization will use Platform Spaces to organize the media they will work on. One method is to establish Platform Spaces per Project, i.e. “Project Spaces”. The other method is to create larger “Buckets” of information and for example put all projects in one Platform Space. There are pro’s and con’s to each approach.
Figure 10 Considerations for Organizing Platform Spaces
Generally, the less Platform Spaces the less control the user has over certain capabilities of the system. These include User Permissions, and Platform Space Features. An example is if the administrator sets up one Platform Space, they can only create one set of user permissions to that Platform Space. Because any user using the system would need access to the Space, all users would effectively have Read/Modify access to the Space. This approach severely limits the flexibility of the system.
However, the more Platform Spaces defined, the more user mount points that exist and that could be open by users at the same time. This can possibly create confusion for users when they have too many mount points. Many users prefer a single mount point because they can have access to all of the data on the storage system at the same time. This is sometimes in conflict with the administrator’s goal of keep data safe and controlling security of the content.
One of the largest considerations is to make sure that the total path length, including all of the directories in the file path, does not exceed 260 characters. If it does, the Platform cannot store files in paths beyond that size.