Running your workspace

For owners and admins: setting up, inviting people, plans, what is recorded, handing over.

Guidance for the person who sets up and runs a workspace in synoia: its owners, and the admins they choose. It covers creating the workspace and its channels, inviting people and guests, deciding who can open what and what your team's AI can reach, plans and storage, what is recorded and who can see it, where your data is and how it is protected, handing over, leaving, and what to do when something goes wrong.

It sits beside Working with your channels, the guide for everyone who uses the app. Where that guide already explains something, this one links to it rather than repeat it.

This guide describes synoia 0.5.0. Where something arrived in a recent release, the guide says which. If your app is older, look in App settings, Updates.

Before you start

Who can own a workspace

A workspace is your team's space in synoia: one member list, its own owners and admins, its channels and who can open each one. Each workspace lives on one server. The person who creates a workspace is its owner.

There are two ways to become an owner while synoia is in its pilot:

We send you a set-up link by email, for the address you will sign in with. The link works for 5 days. If it runs out, reply to the email or write to contact@synoia.app and a new one is sent.
You already have a synoia account, because someone invited you to a workspace, and you create one from the app (see "Create your workspace" below).

Nobody can create an account without an invitation. One person can own up to three workspaces; we can change that limit.

What you need

A Google or Microsoft account with the email address you were invited at. There are no synoia passwords. You always sign in with the address the invitation names; signing in with another address does not find it.
The desktop app. Your notes are read and written there. It runs on macOS 12.3 or later (Apple silicon or Intel), and on Windows 10 or 11, 64-bit. The website's download page offers those two. Windows may warn that the installer is from an unknown publisher: choose More info, then Run anyway.
A browser, for the workspace's pages at synoia.app: People, Guests, Teams, Invitations, Channels and Settings. Everything else is in the app.

If your business uses Microsoft 365

Many businesses only let staff sign in to apps their IT team has approved. If yours does, the first person to sign in with Microsoft sees Your IT team needs to approve synoia in the app. The button Copy the request for IT copies a short note for your IT team. It names the app and its publisher (synoia.app), lists exactly what synoia asks Microsoft for (signing the person in, their name, email address and basic profile, and keeping them signed in), says that synoia does not ask to read anyone's mail, files or calendar, and tells them to grant admin consent in the Microsoft Entra admin centre.

Do this before you invite colleagues, so they are not each stopped at the same screen. Their invitations wait while IT decides. If an address can also sign in with Google, the app offers Or sign in with Google; a Microsoft work address waits for IT.

The set-up link's own sign-in page, on the web, does not show this screen. If Microsoft refuses you there, sign in to the desktop app with Microsoft to get the request for IT, or ask your IT team to approve synoia first.

Owners, admins, members and guests

	Owner	Admin	Member	Guest
Open channels	What they are given	What they are given	What they are given	Only what is shared with them by name
Create channels	Yes	Yes	Yes	No
See every channel's name and who has access	Yes	Yes	Only channels they reach	Only what they reach
Change who can open any channel	Yes	Yes	Only channels where they have Full access	No
Invite members, admins and guests	Yes	Yes	No	No
Change roles, remove people	Yes, including other owners, asked first	Members and guests, not owners or other admins	No	No
Run teams	Yes	Yes	No	No
Name, logo, colours, AI default	Yes	Yes	No	No
See the plan and storage	Yes	Yes	No	No
Delete the workspace	Yes	No	No	No

Owners and admins see the names of every channel and who has access to each. They see what is inside a channel only when they are given access to it. A workspace always keeps at least one owner.

Create your workspace

From your set-up link

Open the link. Sign in with Google or Microsoft, using the address the link was sent to.
Create your workspace asks for its name and, if you like, a logo. The name is shown exactly as you type it, capitals and all. The logo can be PNG, JPEG, WebP or SVG, up to 1 MB; it is cropped to its centre square. Until you add one, the workspace's initials show.
Press Create workspace. You are its owner.
The next page, <workspace> is ready, has two steps: Get the desktop app, then Invite colleagues. Get the app first and make your channels, so colleagues arrive to something.

You can come back to that page from Back to next steps at the foot of the menu on the left of the workspace's pages.

From the app

If you already have an account, press + at the foot of the column of workspaces on the far left, then Create a workspace. It asks which of your accounts owns it (Owned by), its name, an icon and a colour. Press Create workspace.

The Create a workspace box in the app, with a name typed in and the Next button outlined.

Choose where it lives on your computer

The first time you create or join a channel in a workspace, the app asks Where should <workspace> live on this computer? Each workspace has one folder, and every channel is a folder inside it. The default is a new folder named after the workspace in your home folder, outside Documents, because Documents is often kept by iCloud Drive or OneDrive. As the person who leads the workspace you may also choose A folder you already have. Your colleagues choose their own folder on their own computers; nothing you choose here changes theirs.

You can change where new channels go later, in App settings, Workspaces and channels. That moves nothing already on the disk.

Set its name, logo and colours

In the app, click the workspace's name at the top of the sidebar, then Workspace settings, Overview. There you can change the name (Save name), upload a logo, and choose the workspace theme: a Main colour for the tile, buttons and the selected channel, and an optional Accent for links, the cursor and highlights. Press Save theme. Everyone in the workspace sees the theme; each person can still choose their own colours for their own screen.

The same settings are on the website, under Settings, where the logo is called the icon and the main colour is called Colour. Either place changes the same thing.

When you rename the workspace, the app offers once to rename its folder on your computer to match. Nothing is renamed unless you press Rename folder. Each colleague is asked the same about their own folder.

Create your channels

A channel holds notes on one subject, such as Clients or Handbook. Each is a folder of plain markdown files on every computer that has it. Any owner, admin or member can create one.

Click + in the channel column, or Create a new channel on a workspace with no channels yet. Create a channel in <workspace> offers two ways in: From a folder and From a template.

From folders you already have

Choose From a folder and pick a folder. Choose the folders to bring in lists the folder itself, as All of <folder>, as one channel, and each folder inside it as a channel of its own. Tick the ones you want and rename each channel there if you like. A folder that is already a channel is shown greyed and cannot be ticked. If the folder looks like an Obsidian vault, the app says so and lets you choose which folders become channels.

Each row says what will happen to the folder:

Stays where it is, for a folder already inside the workspace's folder.
Moves into <workspace>, for a folder somewhere else on your computer. A shortcut is left at the old place. Nothing is deleted, and until the channel's first upload finishes you can press Move it back.
Copied in, for a folder kept by iCloud, Dropbox, OneDrive, Google Drive, Obsidian Sync or git. The original is not touched and is no longer connected to the channel.

Under Who can open them, choose Only me for now (the default; you share each channel when you are ready) or Everyone (members of the workspace can open and edit them). The count of files that stay on this computer has a link, See which files and why.

Press Create N channels, read the confirmation and confirm. Each channel then comes in on its own row. If one fails, the others carry on; the failed row names the file and offers Try again.

Choose the folders to bring in, with three folders ticked, each marked as moving into the workspace, and the Create 3 channels button outlined.

New in 0.4.0:

If you press Create while offline, the app says you are offline and stops before anything is moved. Try again when you are back online.
When copying a folder stops on one file, the row also offers Leave that file out. The file is not copied, and the original is not touched. For a folder that moves or stays where it is, the row offers Try again only.

The member guide explains which files sync and why some stay on your computer: see Which files sync.

From a template

Choose From a template. The gallery groups templates under Start simply, Just for me, Study, Work and research and Clubs and communities. Each says who it is for, what you get and the folders it makes. Blank is always there. Press Use <template>, give the channel a name and press Create channel.

Coming from Notion, Confluence or SharePoint? There is no importer. Start from a template that fits, then ask your AI to move in what you need; the dialog has a prompt to copy for it.

New in 0.4.0, a template can be a workspace pattern: one choice that makes several channels, so you can share each differently. You choose whether to make them as separate channels or as one channel with folders inside. The first patterns are Small business, Foothold and Second brain.

The member guide says what a new channel holds: see Starting a channel from a template.

A new channel is private to whoever made it

Whoever creates a channel holds Full access to it, and nobody else can open it until it is shared. That includes you as owner, for channels your colleagues make. The channel belongs to the workspace, not the person: if they leave, it stays.

Invite people

Invite colleagues once your first channels exist, so they arrive to something.

Invite members and admins

In the app, click the workspace's name, then Invite people; it opens the website. Or go to People on the website and press Invite people.

Type one or more email addresses, separated by commas. Each person signs in with the address you type.
Choose a Role: Member or Admin. A member can open the channels shared with them. An admin can also invite people and run the workspace.
Under Channels (optional), tick any channel to give it to them when they accept, at Can view or Can edit. A channel set to Private is not offered here; give access to it from the app instead.
Press Create invitations.

Each invitation lasts 5 days and works once, for the address it names.

The Invite people page on the website, with two email addresses typed in, a role chosen and the Create invitations button outlined.

What they receive

synoia emails each invitation, from the address the Invite people page names, and the button reads Send invitations. Invitations ready says "Emailed to" each address, and still shows each link with Copy link, so you can send it another way too. If an email does not go, the page says so: copy the link and send it yourself. Guests you invite from a channel are emailed the same way. The same links are on Invitations until they are accepted or expire.

A server that does not send email (a test server, or one run without an email provider) says "This server does not send email" on these pages, and the button reads Create invitations. Then you copy each link and send it yourself, by your own email or chat.

The link opens a page, Join <workspace>, that names who invited them, the address the invitation is for, its role, and any channels it gives. Anyone holding the link sees this, which is why the link is kept short-lived. Its button, Open in the app, opens the desktop app, which asks them to sign in with that address. If they do not have the app yet, the page links to the download. After they sign in, the app shows the invitation, asks where the workspace should live on their computer, and downloads the channels it gives. Nothing needs to be pasted.

If they open the app without the link, they sign in with the invited address and the invitation is waiting for them.

Invite a guest

A guest is someone from outside your workspace, such as a client or a partner firm, given one channel, folder or note. Guests reach only what is shared with them by name: never what is shared with everyone in the workspace, and never a team. They do not see who else is in the workspace and change nobody's access. A guest does not take a place on your plan.

Owners and admins invite guests:

On the website: Channels, Manage access beside the channel, then Invite a guest by email.
In the app: the channel's settings, Who can open it, then Invite a guest by email, for the whole channel or for the folder or note you have selected.

Choose Can view or Can edit. The link lasts 5 days, works once, and is sent the same way as a member's.

On the website, Guests lists every guest, what each can reach and who invited them. Make a member turns a guest into a member, never straight into an admin or owner. Remove ends all their access at once. When the last thing shared with a guest is taken away, they leave the workspace on their own.

Withdraw an invitation

On the website, Invitations lists every invitation not yet accepted, with its role, channels, who sent it and when it expires. Withdraw stops its link working at once.

When someone cannot get in

What they see	What to do
"That's a different account"	They signed in with another address. They choose to sign in again as the invited one.
"This invitation can't be used"	It expired or was withdrawn. Send a new one.
"No workspace for this address"	No invitation is waiting for the address they used. Check the address, or send one.
"Your IT team needs to approve synoia"	See "If your firm uses Microsoft 365" above.
"This workspace has used its N member places"	Your plan is full. See "Check your plan, places and storage" below.

Decide who can open what

Change someone's role, or remove them

On the website, People lists every member with their role and the channels they reach.

Change role moves a member to admin or back. An admin cannot change another admin; only an owner can.
Make owner makes someone a second owner (see "Hand over ownership").
Remove ends their access and their sessions at once, including through their AI. The channels they made stay with the workspace; where nobody else has Full access to one, it passes to the owners.
Clear name and Clear photo remove a name or photo someone set in this workspace, if it is not suitable.

Each channel has its own access. There are two places to set it.

On the website, Channels lists every channel in the workspace, who made it, and who has access, including channels you were not given. Manage access sets who has the whole channel:

Everyone in <workspace>: Shared (everyone can edit), Read-only (everyone can view, nobody edits unless named) or Private (only the people and teams named). Press Apply to the whole channel.
Give someone access: a person, at Can view, Can edit or Full access. Full access lets them edit everything and decide who can open the channel.
Teams, and guests (see above).

In the app, the channel's settings, Who can open it, does the same for the whole channel, and is the only place to set access on a single folder or note. The member guide explains how folder and note access works, and how Read-only and Private behave: see Who is in a channel, teams and guests and Read-only, and what enforces it.

The channel's settings open at Who can open it, listing everyone in the workspace and the people and team who can open the channel, with Who can open it outlined in the list on the left.

Three things owners often ask:

You do not automatically see inside channels. Owners and admins can change access to any channel, but read only what they are given. To see inside a channel you were not given, give yourself access on Manage access. That change is visible to the channel's people in its access list, and from 0.4.0 it is recorded (see "See what happened").
Private means private from you too. A folder or note set to Private reaches only the people named on it, or given the whole channel by name. Owners and admins are not exempt.
Pictures follow their folder, not the note that shows them. See Where pictures live, and who sees them.

Use teams

A team is a named group of members, such as Bids or Finance. On the website, Teams, then New team. Owners and admins run every team; there is no team lead. Share a channel with a team from Manage access, or a folder or note from the app. Everyone in the team gets that access and loses it when they leave the team. Deleting a team ends everything shared with it at once; nobody keeps access that came only through the team. Guests are never in a team.

How each channel is seen

Every channel is seen by the rest of the workspace in one of four ways: open, read-only, by request or private. An open channel is shared with everyone in the workspace to read and write; a read-only one, to read. A channel open by request shows its name, its description and its people to members, and nothing inside it, and they can ask to join. A private channel is seen only by the people it is shared with. Guests never see a channel open by request. Set it in the app, in the channel's settings, Who can open it.

The default for new channels

The workspace's default decides how a new channel starts: open, read-only, by request or private. Until you change it, the default is private, so a new channel is seen only by whoever made it. Whoever makes a channel can still choose another way when they make it. The setting for owners and admins is being added to Workspace settings; until then the default stays private.

Describe a channel

A channel open by request can carry a short description, up to 280 characters of plain text, so members can tell what it holds before they ask. Someone with Full access types it in the channel's settings, Who can open it, and confirms it before anyone sees it. It is always written by a person, never by AI, and it should say nothing you would not show the whole workspace.

Requests for access

When a member asks to join a channel open by request, the request appears in that channel's settings, Who can open it, under Requests, for the people with Full access. Grant it with Give access, at Can view unless you choose Can edit, or decline it with Decline and an optional reason. The person sees the answer in the app. A request never lets anyone in by itself.

Labels on the atlas

A label is a word for how someone stands with the workspace, such as Supplier or Partner. It grants nothing. Owners and admins set labels in the app, in Workspace settings, People, under Labels, up to 40 characters each. The person sees their own label on the knowledge atlas; owners and admins see everyone's.

Public links

Someone who can manage a note's access can publish it as a public link, which anyone with the link can read without signing in. On a channel set to Private, only owners and admins can publish. A block or Private setting made after a link was published stops it showing the note.

There is no list of every public link in the workspace. To check what is published, ask the people who manage your channels.

Decide what your team's AI can reach

synoia runs no AI of its own over your notes. Each person connects their own AI, such as Claude or ChatGPT, through one connector for their account. Their AI can read and change what they can, and never more. In a channel where they can only view, their AI can only read.

As owner you have two controls:

AI for new channels. Workspace settings, Channels, AI can reach new channels. It applies to channels made from then on and changes none that exist. It is on until you change it.
AI for one channel. In the channel's settings, AI, AI can reach this channel is one switch for everyone who can open the channel, guests included. Owners, admins and anyone with Full access to the channel can change it. It works on the next AI request; nobody needs to reconnect.

The channel's settings open at AI, with the switch AI can reach this channel turned off and outlined.

Each person can also leave a channel out of their own AI. The member guide explains both switches, what the AI is told when a channel is off, and what the switch cannot stop: see Connecting your AI, and switching it off for a channel.

Two points for owners:

The switch stops AI reaching a channel through synoia. It cannot stop an app on someone's own computer opening their synced copy of the channel's files. For material that must stay out of every AI, keep it out of synoia, or out of the channels shared with people who use local AI tools. See The case to be careful about: an offline AI.
"An owner adds the connector first" means your Claude owner. On a Claude Team or Enterprise plan, the owner of your Claude organisation must add synoia as a connector before members can use it. That may not be the same person as your synoia owner.

Check your plan, places and storage

Your plan

Workspace settings, Plan and storage, shows your plan and how much storage is used. The website's Settings page shows more: the plan's state, internal members against the limit, guests, and storage.

Pilot workspaces are on the pilot plan: free, with no limit on people or storage. Storage is still counted and shown.

We change plans; you cannot change it yourself yet. To ask about another plan, write to contact@synoia.app. The plans and prices are at synoia.app's pricing page.

Places for people

Owners, admins and members each take a place on a plan with a limit. Guests do not. When a plan is full, no new member or admin can join, and nobody loses access. Guests can still be invited.

Storage

What counts is the text of your notes and your pictures and PDFs. Version history, deleted items, the search index and the sync engine's records do not. The app shows owners and admins a strip at 80%, 90% and 100%. At 100%, no new pictures or PDFs are added; past 110%, no new notes either. Editing notes that exist is never refused. The member guide has the detail: see Your workspace's storage.

Which file types sync

Which file types sync is set by plan, by us, and can change without a new app. Owners do not choose types. The list for each plan is published at /api/plans/file-types.html on your server; the member guide has the table: see Which files sync.

Scripts (.py, .sh, .plist) sync only on request. We switch them on for your workspace when you ask, and they sync only after an owner has read what that means and confirmed on the website's Settings page, under Scripts. Owners can read every change to a script there, under Changes to scripts. Read Syncing scripts first.

The Scripts section of the website's Settings page: what syncing scripts means, the tick box and the Confirm scripts button, which is outlined.

See what happened

New in 0.4.0.

What synoia records about your workspace

From 0.4.0 synoia keeps an audit log for each workspace. Each entry says who, what, when, and through what (the desktop app, the website, which AI connection, or a session by one of our operators). It records:

signing in and out, and failed sign-ins;
invitations made, accepted and withdrawn;
role and access changes, including an owner or admin changing access to a channel they were not given;
AI connections made, used and disconnected, and every read and write an AI makes through synoia;
opening a note in the app, and every change made in the app;
exports of the log itself;
one of our operators opening a database session for your workspace (see below).

Entries hold ids, not names: no note's name or text is written into the log. The source network address is kept for sign-ins, AI connections and operator sessions only.

The log cannot be changed by anyone, us included. Every five minutes the new entries for your workspace are sealed and a copy is written to storage that cannot be changed or deleted for twelve months, in a separate AWS account that only our founder can read. If an entry cannot be written, the action is refused with a plain message rather than happening unrecorded.

Entries are kept for twelve months, records of what an AI changed included.

What you can see

Owners and admins can export their workspace's log as a CSV file for a date range of up to twelve months. Members can export their own entries. An export is itself recorded.

In 0.4.0 there is no button for the export, and no activity page. The export lists ids rather than names, so it is easier to read alongside your People and Channels pages. Until the app or the website has a way in, write to contact@synoia.app if you need an export.

Before 0.4.0, the only records an owner can read are the changes to scripts, on the website's Settings page.

What we record about our own people

We run the server your workspace is on. Our staff do not read workspace content. From 0.4.0 that promise is backed by a record of every time our people reach the production server:

every login to the server, naming the key used, and every command run with administrator rights;
every database session one of our operators opens. Before it opens, the operator must give a reason, a card or incident number and, for support, the workspace it is for. Operators reach the database as themselves, may only read, and cannot read anyone's sign-in or connector tokens. Every statement they run is logged.

These records leave the server within a minute, to the same write-once storage as the audit log, where nobody on the server can change them. They are kept for twelve months. Only our founder can read that storage. An operator database session opened for your workspace also appears in your workspace's own audit log, so you can see that it happened.

What this does not show: what someone with full control of the server read directly from its disk. It shows that they logged in and what they ran. The next section says what encryption adds.

We watch the servers

From 0.4.0 the production server is checked automatically, and we are alerted if it stops, runs short of disk or memory, misses its nightly backup, or falls behind on security updates. There is no status page you can check.

Look after your data

Where it is

Your notes are plain markdown files on each member's own computer, in the workspace's folder. That is the copy people work in, and it stays theirs if synoia goes away.

The server, which we run, holds the copy that keeps everyone in step: the notes, pictures and files, version history and checkpoints, who has access, and the AI connections. It runs on Amazon Web Services in London.

How it is protected

In transit: every connection is encrypted.
At rest: the server's disk is encrypted.
Your workspace's own key (new in 0.4.0): each workspace has its own encryption key in AWS's key service in London. Note text, files, pictures, version history, checkpoints and the search index are encrypted under it. A copy of the database or a backup cannot be read without it, and one workspace's content cannot be opened with another's key.

What this does not do, said plainly:

We still hold the keys while the server runs. The server has to read your notes to sync them and to answer your team's AI. This protects your content in a copy of the database or a backup, not from us. What protects it from our people is the restricted, recorded access described above.
Names are not encrypted yet. The names of notes, folders, channels and the workspace stay readable on the server.
If the key service cannot be reached, the server refuses to serve or change content, and says so. It never falls back to unencrypted storage. Notes stay on everyone's computer meanwhile.

Backups

The server is backed up every night, encrypted, and each backup is kept for 35 days, in London. We test that a backup can be restored at least every 28 days; from 0.4.0 that test runs on a schedule and opens every workspace's notes with its own key.

A backup restores the whole server, if it is lost. There is no way in synoia to restore one workspace, one channel or one note from a backup. If the server were lost, what changed since the previous night's backup in people, access and settings, and AI changes no computer had yet received, could be lost. Notes would not: every member's computer holds the notes they can read.

Getting things back

One note: its version history, in the note. See Working offline.
A whole channel: the channel's settings, History. A checkpoint captures every note in the channel, content and folders. One is taken automatically each day the channel changes, the channel keeps its five most recent, and owners and admins can take one by hand before a big change. Reverting rolls every member's channel back. Only owners and admins who can open the channel can create, delete or revert to a checkpoint; a person with Full access who is not an owner or admin cannot. Reverting also needs every note in the channel to be readable to you, so in a channel set to Private you revert notes one at a time instead.
A deleted channel: it is gone from the server at once. Each member's copy stays on their computer as a plain folder. To bring the channel back, create a channel from someone's copy (From a folder), then share it again.

Deleted notes and pictures are kept on the server, with their history, and do not count towards storage. There is no way yet for an owner to purge them.

Take a copy of your data

Any channel you can open: its settings, Import and export, Export entire channel… saves a copy of your own copy of the channel to a folder you choose. It holds what you can see in that channel.
Everything at once: there is no export of a whole workspace. Give yourself access to each channel and export each one, or copy the channel folders from your own computer.
People, access and teams cannot be exported. Take them down from the website's People, Guests, Teams and Channels pages.

Hand over ownership

Keep at least two owners. If your only owner leaves the firm, loses their Google or Microsoft account, or is otherwise unreachable, there is no way for anyone else, us included, to make a new owner. An account's email address cannot be changed, so hand over before someone's address stops working.

To hand over:

On the website, People, press Make owner beside the person and confirm. You are both owners now.
Then, on your own row, choose Admin or Member and press Step down. Or leave the workspace: click its name in the app, then Leave <workspace>.

The People page on the website, with the Make owner button outlined beside Tomas Reyes, an admin.

An owner can also change another owner's role or remove them, after a confirmation. A workspace is never left without an owner: the last owner cannot step down, leave or delete their account until another owner exists. If you are the only owner and try to leave, the app says so and offers Make someone an owner.

Leave synoia, or delete things

Delete a channel

In the app, App settings, Workspaces and channels, Delete beside the channel. Type its name to confirm. Owners and admins can delete any channel; the person who made one can delete it while it is still empty. It is deleted for everyone, at once. Everyone else's copy stays on their computer as a plain folder that no longer syncs, and they are told where it is. Your own copy goes to the Bin unless you untick that.

Delete the workspace

Only an owner can. In the app: Workspace settings, Delete workspace, and type its name. On the website: Settings, Delete this workspace.

What goes, for everyone, from the server: every channel and everything in it, its teams, invitations and settings, and everyone's access. Everyone's accounts stay, and so do their other workspaces. The folders on people's computers are not touched; they stop syncing.

It cannot be undone. The deleted content remains in the nightly backups until they expire, 35 days later. From 0.4.0 the workspace's key is also scheduled for deletion, 30 days later, after which no backup of it can be read.

Before you delete, take what you want to keep (see "Take a copy of your data"). There is no export offered at the moment of deletion.

Delete your account

On the website, sign in, then go to /account/delete (it is linked from your profile and home pages). Type your email to confirm. You must have signed in within the last ten minutes; if not, the page asks you to sign in again first.

The page lists what goes and what stays. In short: your membership of every workspace, your sign-ins and sessions, your AI connections and your profiles go. Notes and channels you made stay with their workspace, without your name. The files on your computer stay. You cannot delete your account while you are the only owner of a workspace: hand it over or delete the workspace first.

If your firm leaves synoia

Make sure every channel you want is on at least one computer, or exported (see "Take a copy of your data"). The files are plain markdown, and Obsidian opens them.
Take down who had access to what, if you need it.
Delete the workspace.
Ask each person to delete their account if they have no other workspace.

Your folders keep working as ordinary folders. If someone still uses them in Obsidian, they are unchanged.

When something goes wrong

Look first

Sync status, in the channel's settings, says whether the channel is up to date and, if not, why. See which files and why lists every file that stays on that computer, with the reason.
Someone cannot see a channel: check Who can open it, then the website's Channels page. Remember that a guest never gets what is shared with everyone or with a team.
Someone's AI cannot reach a channel: check the channel's AI page, and ask them whether they have left it out of their own AI.
A colleague's computer shows something different: check both computers are on the same version, in App settings, Updates.

Contact us

Write to contact@synoia.app. A person reads it, usually synoia's founder. Say:

your workspace's name and your app's version;
what you were doing, what you expected, and what happened, with the time;
for a sync problem, the text from Copy diagnostics on the channel's Sync status page.

Copy diagnostics names the channel and the paths of any files with problems. Read it before you send it, and take out anything you do not want to share.

For a security problem, begin the subject line with SECURITY:.

There is no published response time or out-of-hours support. If we need to look at your workspace's records on the server to help, that session is recorded, with its reason, and from 0.4.0 it appears in your workspace's audit log.