Workspaces in Tana
First off - what is a workspace? A workspace is a separate graph in Tana, where you can control who has access, you can create tags for that particular workspace and you can control which, if any, tags from other workspaces you want to allow.
Each workspace has its own library and you can export a JSON structure of the entire workspace.
If you look in your sidebar you can see your private workspace at the top. This is your personal workspace, and it cannot be shared with anyone else. Anything you put in here, must explicitly be shared with other workspaces, so you can be sure that data from this workspace won't be seen by others.
In the bottom of the sidebar, you will find a plus-sign where you can accept invites to workspaces created by others, or you can create your own workspaces. Workspaces you create or accept invites from will be shown beneath you private space.
Let's go ahead and create a workspace to share with your team:
To effectively work with multiple workspaces, it's best to create supertags in the workspace where you want the shared data to live. You can still use the tags in other workspaces, but if you create a tag in your personal workspace and use it in a shared workspace, only YOU will see that tag. Similarly if you link a node from your workspace without moving it over, the title of the node will show, but only you will be able to expand and see the content of the node.
To create a shared tag, simply create the tag in the shared workspace.
Now that we have created this tag, you can add nodes with this tag directly in the shared workspace...
.. or you can create it in your personal workspace.
BUT you need to keep in mind that ONLY YOU can see this information for now.
You'll notice that there's a suggestive action to move the node to the shared workspace. If you click this, the node will be moved to the shared workspace, but a reference link will still be there in your personal workspace. This is very convenient, since it allows you to draft everything up and THEN send it over to the workspace when you're ready to share.
In all workspaces, including your private space, there is a setting to control which workspace tags should be used.
You can also move nodes to another workspace with the "Move to" command. By default you have the option to move node to the target workspace Home node, Today or Library. But if you open the shared workspace and click settings, you can create other move targets by either copying or pasting the nodes you want as targets or by @-mentioning them
The Home node is the root node to all other nodes that exist in a Workspace.
The workspace at the top of the sidebar is your personal workspace, which no one but you can see the contents of. Clicking your personal workspace will send you to your home, which acts like the base of your platform.
Workspace profile: This defaults to the initials of the Workspace name. You can replace it with an image by clicking it and uploading a new picture.
Schema: The place where all supertag definitions are saved when creating them. Field definitions can also be saved to Schema if you choose - via the field configuration panel.
Library: Created items that don't live in a specific context.
Settings: The personal preferences to your account/workspace, such as your custom keyboard shortcuts.
Options > Allow content from... is where you can control which workspaces you see references from within this workspace. When you are a member of several workspaces, this controls what content is available to you when you look for nodes via @, or make search queries.
The nodes on your Home node also form the list of nodes you'll see when you expand the workspace node in the sidebar.
It is not possible to change which workspace's day node you open by default; it is fixed to your private workspace's day node.
However, open the sidebar and hold
Option (Mac) or
Alt (Windows) whilst clicking on a workspace in your sidebar to open its day node for today.
Absolutely: The most common place to do this is on the Home node. Here are some examples of top level wiki structures, usually arranged on workspace home nodes:
As of February 2024, when a workspace hits 500k nodes, the API will not sync any new information to the workspace anymore.
The 500k node limit per workspace only applies when information is being added from an external service like our Input API or Readwise. This is a temporary precaution we've put in place to prevent external services from overloading Tana while we're still at the pre-launch stage.
You can still use a workspace that has well over 500k nodes as long as you're writing things yourself. There's no performance hit at that mark.