Skip to main content

Finding and recovering content

Search, at the top of the sidebar or on Ctrl K (⌘K on a Mac), matches document names and the folders they sit in. It does not look inside documents, and it does not match tags, descriptions, or a document’s type.So if you remember a phrase but not the document it sits in, search in the app will not find it.Your agents can search the text of every document. Ask yours: “Find the document where we wrote about the enterprise discount.”More detail in Finding documents.
Straight after a delete, the message Deleted "…" at the bottom of the screen has an Undo button. It stays for about five seconds, and longer while you point at it. Select Undo and the document or folder comes back where it was.Once that message has gone, the web app cannot bring it back. There is no trash and no restore button.Deleted content is kept, not destroyed, so a connected agent can still recover some of it:
  • A folder comes back, with everything deleted inside it, when you tell the agent what it was called and where it lived.
  • A document comes back only if the agent already knows its id, for example because it deleted the document itself in the same conversation. Deleted documents can’t be found by searching.
More detail in Getting something back later.

Organizing

The web app has no way to move a folder. There is no drag for folder rows and no menu item for it. Moving a folder is only possible through a connected agent. Ask it to move the folder, and the move updates the paths of everything inside.Documents are different: you can drag a document onto any folder row in the sidebar, or use Move… in its menu.Renaming a folder in the app does work, and it updates the paths of every document and sub-folder inside it.More detail in Folders and organization.
In the web app, only an empty folder can be deleted. For a folder that still holds documents or sub-folders, Delete in its menu is greyed out and marked Not empty.Two ways forward:
  • Empty the folder first (move its contents elsewhere or delete them), then delete the folder.
  • Ask a connected agent to delete it. An agent can remove a folder together with everything in it, which is the practical route for a large branch. It confirms first: the agent reports how many documents and sub-folders would go, and only removes them once you confirm.
If the folder contains a locked document anywhere inside it, the agent’s delete is refused too, naming the locked documents, until they are unlocked.More detail in Deleting documents and folders.

Saving and rendering

Tatara saves as you type and shows where it has got to in the status line along the bottom of the window: Saving, Saved, Synced, or Failed. Failed means the last change did not reach the server. When the server refused it, a message says why.The usual causes:
  • You lost your connection. Check it, then make the change again.
  • Your account is over its plan’s document limit. The message starts This account is over its. Over the limit, documents are read-only until you upgrade or delete some, and creating one is refused with a message starting Document limit reached. Reads and deletes keep working at any level, so you can always free up space. Settings → Billing shows Documents used against your plan’s limit.
See Plans and limits.
The document is locked. A locked document is approved content that refuses every change: the title can’t be edited, the body doesn’t accept typing, and the details rail is read-only. A prose document says Locked. Unlock it to edit. above its body.Only the document’s owner or an account owner can unlock it, from the padlock in the document’s top bar, next to the star. If you are neither, the padlock is lit but does nothing, and pointing at it says Only the document owner or an account owner can unlock it. Ask one of them.A locked document also cannot be renamed, moved, or deleted, and a folder that contains one cannot be renamed, moved, or deleted either.More detail in Writing and editing documents.
The document could not be shown in its format, so the app fell back to a plain editor. A card headed View names the format the document is meant to render as and says it is Showing plain markdown instead, usually with a short note on what went wrong. Most often an edit broke the structure the view depends on.Nothing is lost. The document is intact and still readable, and the view returns on its own once the document is valid again.The quickest fix is to ask your agent: “This tracker isn’t rendering. Can you repair it?” It can see what is wrong and put it right.More detail in Document formats.
This whiteboard can't be drawn. Its stored content is below. means the whiteboard’s stored content could not be read as a whiteboard. Nothing is lost: the page shows what is stored, as plain text.Ask your agent to repair it: “This whiteboard won’t draw. Can you fix it?”More detail in Whiteboards.
HTML documents run in a sandbox that blocks requests to other sites. That keeps a page in your workspace from sending your data anywhere, but it also means a page built to load live data or call another service when it opens will be missing those parts.Ask your agent to rebuild it: “This report isn’t displaying properly. Rebuild it with everything built into the page.” Your agent knows the rules it has to meet, and Tatara checks the new version in a browser and reports any errors back to it.If the page says Couldn't load the HTML., choose Retry, which reloads the page. If that keeps happening, your network or a browser extension may be blocking the separate address that HTML documents load from.More detail in HTML documents.

Account and access

When an invitation can’t be sent, the reason shows under the email field in Settings → Members. The most common one starts Author seat limit reached. Your plan’s seats are all taken by active members and pending invitations.A pending invitation holds its seat until it is accepted or revoked, even after it has expired. Revoking an invitation nobody is going to accept frees a seat at once. Otherwise deactivate someone who no longer needs access, or move to a plan with more seats.Only owners can invite. If you don’t see Invite a teammate, you are a member; ask an owner.More detail in Members and roles.
An owner of your account deactivated your membership, and you belong to no other active account. Your profile still exists, but it can’t reach that account’s workspace.Contact an owner of the account. They can select Reactivate on your row in Settings → Members, which restores your access with the role you had.More detail in Remove someone’s access.
On the sign-in page, choose Forgot password?, enter your email and choose Send reset link. The email’s link opens Choose a new password, where you set a new one of at least 8 characters with Set new password.A reset link works once. If it says This link is invalid or expired, choose Request a new link.

Agents

A rejected write is a normal step in a working agent loop, not a fault. Every rejection states what is wrong and how to fix it, so a capable agent corrects itself and retries without your help. If your agent stops and reports the rejection to you, reading it usually tells you exactly what to ask for.If an agent keeps failing the same write, the usual cause is that it is retrying without reading the response. The agent skills teach it the document formats and the recovery loop up front.One rejection is not for the agent to fix: a write to a locked document. The rejection tells the agent to stop and hand the decision to you, because only the document’s owner or an account owner can unlock it, in the web app. An agent that responds by writing a modified copy of the document somewhere else is working around the lock, and the rejection explicitly tells it not to.
Check the server address first. It is exactly https://www.tatara.app/api/mcp. No other host or path works.If the browser sign-in shows This sign-in request has expired, start the connection again from your client. If it shows Finish setup first, your profile has no account yet: choose Finish setup, name your company, then start the connection again.If the client cannot complete the browser sign-in at all, use an access token instead: create one under Settings → Access tokens and configure the client to send it as a bearer credential. Only an account owner can create one.If an agent that used to work suddenly loses access, look under Settings → Access tokens and Settings → Agent access. Agent access lists only the connections you made yourself, so ask whoever connected the agent to check theirs. Revoking a token or disconnecting a browser-signed-in client cuts the agent off on its very next request. Re-authenticating the client’s entry ends its old connection the same way.If the person who connected the agent was deactivated in that account, they lose access to its workspace, and so does every agent they connected through the browser. An account owner can reactivate them from Settings → Members.More detail in Connecting an agent.
Each connection is locked to the workspace chosen on the consent screen, and the agent cannot switch on its own. If you picked the wrong one, re-authenticate the entry from your client and choose the right workspace. That ends the old connection. To use both workspaces, add a separate entry for the second one instead, with a different name and the same address.More detail in One entry per workspace.