Question
- Can you build a wiki in Tana?Sep 26, 2024
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:
- Should I have just one or multiple workspaces?Sep 26, 2024
We suggest you keep one workspace until you need to do one of the following things, many of which will trigger/require the creation of a new workspace anyways:
- Collaborate with someone in Tana (requires you or the other to create a workspace and invite each other to)
- Import content from Roam, Logseq, Workflowy, or other (this automatically creates a new workspace for the purpose of the import)
- Create a holding space (separate from you private workspace with no "Allow access from.." for testing other people's templates and setups before you bring it in to your active workspaces)
- Creating a Tana Template (which means you want a clean, self-contained workspace setup so you know you're creating a template with no references pointing to other workspaces)
Source of FAQ: Tana Community Resource Hub
- Can I open the day node of another workspace by default?Sep 26, 2024
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) orAlt
(Windows) whilst clicking on a workspace in your sidebar to open its day node for today. - How do I share a supertag from my private workspace to a shared one?Sep 26, 2024
Currently, the easiest and most foolproof way to do this is to not share it but instead build the supertag, with its fields and anything else necessary for the supertag to work, from the ground up in the new space.
That said, if you still want to move a supertag over that exists only in your private workspace, the main work is to ensure that there's nothing in the supertag that references something in your private workspace, otherwise it will appear as broken to others once it's moved.
It's like packaging up a zip file. You can't just zip up a bunch of shortcuts, you need the real files in there or the recipient will only see broken shortcuts.
You'll also have to remember to move over other things like field options, commands, and ensure that no saved view options contain elements from your workspace. Basically, you must ensure that nothing you're moving over from your workspace contains references from your workspace.
To bring all nodes (except system nodes) into the supertags, fields and commands you want to move, use the command "Bring referenced node here". Alternatively, you can move each necessary node separately too if you for example want the field definition to exist outside the supertag. But the key is that everything that is connected to what you're sending over gets sent over too, otherwise there will be missing pieces.
- Does Tana have a 500k node limit?Sep 26, 2024
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.
- How are AI credits used on shared workspaces?Sep 05, 2024
Whoever triggers the request for an AI command or adds the Meeting agent will have the credits charged to their account.
- Why can I not drag nodes from one workspace to another?Jan 11, 2024
In regards to error messages:
- Cannot move notes between different shared areas
- Cannot move nodes between different workspaces - use move command
The reason for this message is that nodes are not made to easily move between workspaces. The workspace they belong to dictates a lot of things, such as permission to view and edit. This will become more important in the future when we build up the collaboration functionality but for now there are a couple of methods you can use to move nodes from one workspace to the other:
- Option 1: Cut (Cmd/Ctrl+X) and Paste (Cmd/Ctrl+V) into new workspace
- Option 2: Cmd/Ctrl+K > Move node to > choose workspace and target (you can set custom targets in addition to the defaults of Today/Library/Home etc)