I'm trying to find if there is a formal description of what I've tried to call the "workspace pattern", seen in apps like Figma, Canva, Notion, etc.
In this pattern, users to start out on their own, with objects that belong to them (designs, documents, etc). Users may or may not be able to invite other users to collaborate with them within their own space: the restriction may be a design choice or an upgrade path. Later, a user can join a larger organization, and have access to objects that belong to their team or the organization's. Typically the division between a user's own objects and objects belonging to others in the same organization is called a "workspace" or a "space", to indicate that there's a strong divider in between.
This pattern is used in applications to allow users to separate and organize their work into separate workspaces, and is commonly used in collaboration tools. A workspace provides a designated area for a user to work on their own projects and to collaborate with other users in a shared area.
The Workspace Pattern enables users to have their own space within a shared environment, allowing them to work independently and also collaborate with others. It allows users to create, edit, and organize their own content, as well as to access and edit content that is shared with them.
In this pattern, a user's work is organized into a hierarchical structure, with each workspace containing multiple objects (e.g., documents, designs, projects) and users having different levels of access to those objects based on their roles and permissions. This pattern allows for greater flexibility and control over user access to content, and can be useful for managing large, complex projects that require collaboration across multiple teams and individuals.
I've described it this way, but are there any other resources that showcase examples or have a more detailed analysis of the design choices and implications?
