Search site

Type a word or phrase to search public pages.

    Workspaces

    Keep related knowledge, people, and rules in one place you control.

    Your boundary

    A workspace brings facts, documents, and media together with their membership and history. Use one for a project, a team, an organization, or a shared activity. Each workspace has its own owner and access rules.

    Connected, on your terms

    Keep a workspace private, share it with selected collaborators, restrict participation to an organization or community, or publish knowledge openly. The workspace model stays the same; you choose its membership and access rules.

    Connecting workspaces does not open their contents. A law firm’s confidential casework, a workspace shared with its client, and a public legal reference can remain connected while each keeps its own access boundary.

    One body of knowledge

    A mortgage workspace can hold payslips, bank statements, and the facts extracted from them. A quote can refer to the documents behind its figures. Files are graph values, connected to the people and decisions they concern.

    Enable Drive to organize those files in directories or bring in a SharePoint library.

    Adopt apps from the registry for the work you need. Different apps operate on the workspace's knowledge through their authorized actions.

    Control where it lives

    Choose the hosts that process your workspace and the storage providers that hold its encrypted copies. Those are different responsibilities: a query host needs permission to decrypt, while a storage provider need not see the contents.

    Encryption explains that trust boundary. Peer-to-peer networking explains placement and replication.

    Open access standards

    A workspace builds on the Solid pod model through Linked Web Storage, adding governed knowledge and execution. Its resource interface is independent of physical storage.

    For a hands-on introduction, read the workspace guide.

    Developer reference

    Technical details

    Isolation and composition

    A workspace binds stable identity, membership, encryption authority and versioned branches. RDF named graphs and file-valued literals share its transaction boundary; Apps consume that corpus.

    Cross-workspace joins preserve independent authorization scopes. Linking IRIs does not union memberships or deliver content keys. A read must identify dataset, branch/commit and actor authority in each source.

    Placement versus disclosure

    Host selection determines plaintext execution location. Custody placement determines encrypted block locations. Private, shared, restricted and public exposure are policy choices over the same container model. Publishing metadata or a selected read surface does not publish the underlying workspace wholesale.