Organizations
An organization is a shared workspace with its own contacts and notes, kept separate from your personal one — how you switch into it, how a contact gets contributed, and exactly who can read what.
What an organization is
An organization is a second workspace. It sits beside your personal one, it holds its own contacts and its own notes, and you move between the two with the workspace switcher.
The two never blend. Switching to an organization does not add badges to your personal list — it swaps the whole view. Your people become the organization's people, your notes become the organization's notes, search searches the organization, and switching back returns you to exactly what you had.
Joining an organization shares nothing
Being added to an organization does not hand over your contacts. Your own contacts and notes stay yours, in your own workspace, and nobody in the organization can see them. A contact reaches the organization only when you deliberately contribute it — one person at a time, from a screen that tells you what is about to travel.
Getting one
Organizations are on the Team plan, and they are not self-serve. There is no button that creates one. A Dhaga admin provisions the organization, sets how many seats it has paid for, and makes someone its owner — so getting started is a conversation, not a checkout. The pricing page's Team card is a Contact sales link for that reason.
Every seat carries the same allowance a Power plan does — 1,000 AI credits per person per month, per seat and never pooled. If you also pay for Dhaga personally, your own plan always wins: an organization seat can raise what you get, never lower it.
Two smaller things worth knowing about credits:
- Switching workspaces changes your allowance, not your usage. What you have already spent this month comes with you.
- Your organization cannot see your AI usage.
Switching workspaces
The switcher is pinned in the app shell — in the rail on a wide screen, in the navigation sheet on a narrow one. It is there even when you belong to no organization, so nothing new ever appears on the day you are added to your first one.
Whatever it says is the workspace you are in. Everything else on the screen follows it.
Members, roles and invitations
The Organization screen (/app/org) is the console. Every member can see the
roster — being put into a workspace and not being allowed to see who else is in
it is not privacy — but the controls are for managers only.
| Role | What it can do |
|---|---|
| Owner | Manages the organization, its members and its single sign-on. Can export the organization's data. Can read every note in the workspace, published or not. |
| Admin | Can invite and remove members. Cannot change an owner. |
| Member | Uses the organization's plan. Manages nothing. |
Inviting. An owner or admin invites by email address. The invitation is sent as mail, and it is also listed in the console with a link the owner can copy and send another way. An invitation consumes a seat while it is pending, so an organization with one free seat cannot have five invitations outstanding.
Accepting. The invite link survives signing in: if you are not logged in when you open it, you land back on the invitation after you sign in rather than on the dashboard. On the hosted service an invitation also grants approval past the signup waiting list — somebody has already paid for that seat and named that address.
Leaving and being removed. Both are ordinary. You keep your personal workspace and everything in it; you simply stop being able to reach the organization's. Mail goes out when you are added, when single sign-on auto-provisions your account, when you are made an owner, and when you leave or are removed.
Contributing a contact
With an organization active, a personal contact's page offers Copy to <organization>. That is the only way a person reaches the organization.
It is a copy, and that is the whole design. Your personal record is not touched, not moved and not emptied. The organization gets a new record of the same human, and from that moment the two are independent: different notes, different facts, nothing syncing them, for ever. You keep everything you had. If you leave the organization one day, your own record of that person goes on being yours.
The picker decides what travels. Everything is ticked by default, and you can untick any of it:
| Item | What it is |
|---|---|
| Notes | Everything you have written about them |
| Facts | What Dhaga extracted from those notes |
| Follow-ups | Open and completed tasks about them |
| Work history | Roles, titles and dates — the employer travels too, so a title says where |
| Relationships | How they connect to people and places |
| Tags | The labels you have put on them |
| Files and scans | Attachments and any scanned card or badge |
| Signals | Job-change and news hits from the watchlist |
A few consequences, said plainly rather than discovered:
- Relationships to people who did not travel are dropped. An edge only survives when the organization holds both ends. Cloning the far end would put people into a workspace nobody chose to contribute them to.
- There is no duplicate check. If a colleague has already contributed the same person, the organization ends up with two records. That is deliberate — duplicate detection already runs inside the workspace, it will surface the pair, and merge handles it. "Is this the same person" is a judgement, and the moment of copying is the worst moment to make it.
- Employers are shared. Colleagues at one company land on one company record in the organization, rather than one each.
- It only goes one way. Personal → organization. An organization's contact cannot be copied back to personal, or on to a second organization.
Contributing a group
Copying a contact never drags its groups along, and copying a group takes the members you leave ticked with it. Both halves are deliberate: contributing a person is one decision about that person, and contributing a group is one decision about the group.
A group copy carries the group itself, its current members, the group's shared notes and tasks, and the relationships between the members that travelled. Group tags do not travel.
Who can read your notes
This is the part worth reading twice.
Everything written or copied into an organization starts unshared. A note you dictate in an organization workspace, and every note that arrives with a copied contact, is marked "Not shared with colleagues" until you publish it.
- Colleagues see nothing until you publish. Not the note, not the facts drawn from it, and not through search.
- The organization's owner can read it anyway — published or not. It is not called "Private" anywhere in the product for exactly that reason, and the owner's access is stated beside the label, above the note composer, and on the privacy page.
- Publishing carries more than the note. Its facts and its place in search go with it, so colleagues can then find the note by searching. That is said on the button before you press it.
- You can unshare again. It takes the note back out of colleagues' view from now on. It cannot unsee: anyone who already read it still knows what it said, and the product says so at the moment you click rather than implying a recall.
- Only the author changes a note's sharing. The owner can read an unpublished note but cannot publish it — reading is the oversight the role was given; publishing it to colleagues in your name would be speaking for you.
Inside the organization every member can read everything that has been published, and can edit and delete only what they wrote themselves.
Deleting an organization's contact
You can forget a contact in an organization when you are the one who contributed it, and Dhaga refuses when it cannot prove you authored it — a refusal with a sentence in it, rather than a silent no-op.
If a colleague has since written their own notes on that contact, the delete is blocked and says so. Their notes are theirs; removing the person underneath them is not yours to do.
Calendars, address books and phone capture
Connections belong to a workspace. A calendar or address book you connected personally is not the organization's, and vice versa — even for the same Google account. Being invited into an organization means connecting again inside it, and the screen tells you which workspace you are connecting to.
An organization's own connection syncs two ways; nothing the organization owns is ever written out to a personal connection.
WhatsApp and Telegram capture is the deliberate opposite. One number maps to exactly one account, so capture lands in your personal workspace by default — always, and however the message arrives. To send a capture to an organization, start the first message with the organization's slug:
@acme met <name> at the summit, wants a demo in March@personal forces the other direction and always wins. Anything that fails to
resolve — an unknown slug, an organization you have left — quietly lands in
personal, and the reply tells you where it went. Personal is the only default
that cannot disclose something by accident.
Exports
Your own export is unchanged and always available: your personal workspace, all of it, whenever you want it.
The organization's export is the owner's and nobody else's, including admins. Every export is recorded in the organization's activity log before a single row is read.
Single sign-on
An organization's owner can connect a SAML or OIDC identity provider from Organization → Single sign-on, and claim an email domain by publishing a DNS TXT record. People signing in through the provider are provisioned as members automatically.
SSO has not been run against a real identity provider
It is built and it is wired, but it has not yet been validated end to end against a production IdP. Talk to us before you plan a rollout around it.
What is not there yet
Stated rather than left to be discovered:
- A copied contact does not appear in colleagues' semantic search until its notes are published. That is the fail-closed side of the visibility rule working as intended.
- You cannot add a note, task or file to a contact a colleague contributed. You can read theirs; writing onto someone else's org contact is not wired yet.
- Company and entity note lists are not workspace-scoped — only contact timelines, lists and search are.
- Calendar reads are not workspace-scoped, only calendar writes. Free/busy and the home tiles still read every calendar you have connected. That is your own data either way.
- Hand-typed facts with no source note do not travel in a copy, because a fact is published through the note that vouches for it.
- The organization's activity log has no screen yet. Copies, publishes, deletions and exports are all recorded; nothing renders them.
- There is no self-serve way to buy, resize or cancel a team. Every one of those is an admin action today.