WHAT: Site-level spaces are anchored at the top of the site hierarchy. They have metadata manager and download catalogs that will cascade down and apply to all of the subspaces created within them.
Only site admins can create and delete site-level spaces.
Chorus is designed to allow site admins to pass responsibility for subspaces to users, so that they can take responsibility for their own part of the system.
WHY: Top-level spaces are significant because of their position at the highest level of the site. They are likely to contain large quantities of files, and are also likely to be the home spaces of multiple users.
Subspaces are important in Chorus. Subspaces can have their own managers, and they don't need to be site admins. This means you can let teams and departments be autonomous in subspaces, and relieve site admins of minor administrative tasks. Use subspaces more often than top-level spaces for better overall management of your Chorus site.
You are here:
