12. Running it

Team, organisations, permissions, obligations, and the things you hope never to need.


12.1 Your team

Settings → Team. Invite people by email. Three roles:

Role Can
Owner Everything, including billing and deleting the organisation
Admin Everything operational — settings, modules, automations, team
Member Day-to-day work; not settings, not deleting

Roles are enforced throughout, not just in the menu. A member who guesses a settings URL gets nowhere.

Who can delete

Deleting needs its own permission, Delete records. Owners and admins have it from the start; a member gets it only when an owner or admin switches it on for them in Settings → Team. Without it, the delete buttons are not shown, and a deletion attempted any other way is refused with the name of the missing permission.

It covers the team's work: contacts, companies, deals, notes, orders, tasks, events, courses, products, donations, conversations and their messages, files, groups, candidates, tickets, tags, drafts, and taking someone off an event or a course. Contacts, companies, deals, notes and orders go to the recycle bin, where anyone can restore them; everything else is deleted for good when you confirm.

A contact you restore counts towards your plan again, because contacts in the recycle bin do not. When the plan is full, the contact stays in the bin and the message says how many fit. "Restore everything this app deleted" first says how many contacts it would bring back and how many more fit, and restores them only when you confirm; if they do not all fit, it restores none.

Editing is not deleting and stays open to every member, and so does taking a tag off a contact, or a person out of a group or a conversation. Campaigns and sequences have their own permission, Delete campaigns, sequences and campaign results. Emptying the recycle bin for good needs Bulk deletion and emptying the recycle bin, and only the owner can delete the organisation itself.

An assistant you connect from Settings → Connected apps can never do more than you: if you cannot delete, it cannot delete for you.


12.2 More than one organisation

One login can hold several organisations. Switch between them from the selector at the bottom of the sidebar; each has its own contacts, modules, terminology, plan and team.

Three things make this practical rather than merely possible:

All organisations — a single view of contacts and reminders across every organisation you belong to. Useful first thing in the morning, when the question is "what needs me today" rather than "what needs me in this particular organisation".

My network — import contacts from one of your organisations into another. If you run a consultancy and a charity and the same person appears in both, you do not type them twice.

Isolation is real, not visual. Switching organisations is not a filter. While you are signed in, the database itself will not return another organisation's rows, so there is no configuration mistake that can make them bleed into each other. The API and connected AI agents work through our server instead, and there the code limits every request to the organisation its key belongs to (12.5).

Deleting an organisation

Only the owner can delete an organisation. It is in two places: Settings → Organisation, at the top of the settings page, and Delete this organisation at the bottom of the organisation selector. You confirm by typing the organisation's name exactly as it is shown; the button stays off until what you typed matches. Curly quotes and apostrophes typed by a phone count as the plain ones they look like; capital letters do count, because you can see them.

Deleting is not immediate. The organisation goes into a bin for 30 days, and during that time:

  • nothing is sent from it — no email, campaign, sequence step, automation, review request, invitation reminder, Telegram or WhatsApp message, webhook or daily task email;
  • nobody can open it, and its API keys, forms, booking pages, invoices, quotes and certificates stop working;
  • nothing in it changes, so the owner can restore it from Deleted organisations in the selector (or /organizations) exactly as it was.

The one exception is a person asking not to be contacted: an unsubscribe from an old email is still recorded, so a restored organisation cannot write to someone who asked it to stop. Anything that was scheduled to go out while the organisation was deleted — campaigns, sequence emails, webhook deliveries, review requests and reminders — did not go out, and goes out at the next run after the restore; the restore button says so, with the number of campaigns and sequence emails waiting.

After 30 days the organisation is deleted for good, with everything in it, as the Terms (§17) say. Export it first from Settings → Backup if you may need the data.

You are never signed out by a deletion. If you belong to another organisation you are moved into it — the one you joined first; if not, you land on a page where you can create a new one. That page also lists your other organisations, each with an Open button. The same happens to everyone else who was working in the deleted organisation, the next time they open anything.

An organisation with a paid plan that still renews cannot be deleted: cancel the plan in Settings → Billing first, because deleting the organisation would not stop the payments.


12.3 Field visibility

The owner can hide groups of contact details from admins or from members, in Settings → Field permissions. It comes with the Medium business plan. The owner always sees everything, and only the owner can change these settings.

Three groups can be hidden, each separately for admins and for members:

  • Relational: the tags and companies on a contact.
  • Marketing: the lead score and the email history on a contact.
  • Custom fields: your organisation's own fields, on contacts.

Someone with a hidden group doesn't see it on the contact page, in the contact form or in the contact list, and sees a short line saying that some details are hidden for their role. They can't change what they can't see. With Relational hidden, a company's page doesn't show its people either. Tags, companies and custom fields are locked in the database too, not just left off the screen.

A new contact that someone imports, or scans from a business card, still gets its company, and from a card its event tag, so the record stays complete.

Nothing is hidden until the owner hides it. Showing a group again works on any plan, so an organisation that leaves Medium business is never stuck with settings it can't undo.

API keys and connected assistants see what the person behind them sees: a key, what the person who created it sees; a connected assistant, what the person who connected it sees. What is hidden is left out of their answers, with a note saying what is missing, and a request that would read or change it is refused. A key whose creator has left the organisation sees none of these groups. The full export, from Settings → Backup & Export or through the API, leaves out what is hidden in the same way.

Not yet covered: pages that are not about a single contact, such as Campaigns, Reports and the pipeline, keep the permissions in Settings → Team. Names, emails and phone numbers can't be hidden yet.


12.4 Consent and the right to be forgotten

Two GDPR obligations, handled properly rather than as a checkbox.

Consent is logged append-only. Every consent and every withdrawal is a new, timestamped entry. Nobody on your team can edit or delete one, so you can always show what was agreed and when. An editable consent record proves nothing; this one is a real audit trail. The record lives as long as the contact: erasing the person removes it with them.

Your website can send the proof with it. If your own website collects marketing consent in a form, its server can send CRM City the proof of each submission, with your secret API key: the exact words the person was shown, the boxes they ticked, the versions of the form and of your privacy notice, the page and the time (POST /api/crm/contacts/:id/consent-proofs, on /developers). A proof without the words shown, or without those versions, is refused. Proofs are only ever added: nobody can change or delete one, except by erasing the person. A proof of consent or of a refusal also updates the consent shown on the contact, marked "website form"; a soft opt-in (an existing customer, offered a way to refuse) is kept as its own basis and is not shown as consent. A proof records the choice; it does not switch marketing on or off for that person.

Erasure is real deletion. Chapter 2 covered the two levels: delete is recoverable, erase is permanent. Erase is the right-to-be-forgotten implementation, which is why it makes you type a confirmation phrase including the person's name.

Also relevant: every marketing email carries an unsubscribe link (one click on it stops your marketing to that person, and clicking again does nothing more), the do-not-email list is honoured by every marketing sender in the product, and full export is on every plan, Free included, for the owner and for admins with the Backups and GDPR exports permission. Bounces and complaints on mail sent through your own email account stay on that account, which stops sending to those addresses (chapter 5.3).


12.5 Security

Two-factor authentication is available per user, using an authenticator app. Turn it on in your account. If you handle other people's personal data — and you do, that is what a CRM is — turn it on.

The audit log records sensitive operations: merges, permission changes, hierarchy edits, key management. Append-only, browsable by admins at Settings → Audit. It exists to answer "who changed this and when" without anyone having to remember.

Isolation is enforced by the database for everything a signed-in session reads and writes. Described in chapter 2 and mentioned again here because it is the single most important security property of the product: for that session, a bug in the application cannot reach another organisation's data, because the rule is enforced one layer below the application. Some work runs on our server's own connection, which the database rule does not cover: the API, connected AI agents (chapter 13) and some actions in the app. There the application checks the organisation on every request, so isolation on those paths rests on the code.

The same wall holds for the direct links between records. When one record points at another (a deal at its contact and company, a task at the contact it is about, a tag on a contact, an invoice at its customer), both must belong to the same organisation: the database refuses a link to another organisation's record, whatever the application asks. References kept inside settings or flexible fields, such as the steps of an automation or the record a custom field value is attached to, are not links the database can see, so the application checks those instead. The people on your team are the one exception to the database rule, because the same person can belong to several of your organisations.


12.6 Backup and leaving

Settings → Backup downloads every record you have put in: contacts, companies, deals, invoices, activities and settings, each kind of record as its own table. Files you uploaded are listed in it by name; download the files themselves from each contact or company page. Live credentials (your Telegram bot token, your WhatsApp app secret, the API key of your email account) stay out of the file and stay yours — regenerate them in Settings, or at your email provider. The API export carries every row of the organisation; the Settings file carries only your own rows of the few tables that belong to one person. Any conversation can also be exported as a transcript on its own.

The file carries each table twice: as spreadsheet-ready CSV and as raw data. In the CSV, a text value that starts with =, +, - or @ gets an apostrophe in front, so a spreadsheet shows it as text instead of running it as a formula; a plain number like -12.5 is left alone. The raw data keeps every value exactly as it is stored.

The phrase on that page is deliberate — leave whenever you want; what's yours goes with you. Full export of your records is a design principle rather than a feature request that got built.

It is also, honestly, a sales argument. Moving into a CRM is frightening because moving out of one usually is. Knowing the exit exists is what makes the entrance safe.


12.7 Your plan

Settings → Billing. Your current plan, each plan's limits, and the upgrade path. Compare what each plan includes opens the pricing page, feature by feature. Payment goes through Stripe; card details never touch this product.

Plans are per organisation, and so are the invoices. Each organisation in your account has its own plan, its own limits (except the free contacts, below), its own subscription and its own invoice — buying Freelancer / Solopreneur for one does not upgrade the others. That is deliberate: each organisation is its own entity, with its own accounting and its own money, and a separate invoice is what lets you put the expense through the right books.

The upgrade buttons appear only on the free plan. Once an organisation has a subscription, every change — up, down, or cancelling — goes through «Manage subscription» (the Stripe customer portal), which prorates fairly and closes the old subscription properly. Cancelling does not delete anything — you drop to the free plan and your data stays. The portal is also where you update your card and see invoices.

Plans limit users, contacts, automations and sequences. Hitting a limit stops you creating new things; it never breaks what exists. People who come to you on their own, through a form, a booking, an email or a message, are still added past the contacts limit, and Contacts and Billing tell you when you are over it.

Free organisations share one allowance of contacts. You can own up to two organisations on the Free plan, and the 200 free contacts are yours, not each organisation's: every Free organisation you own draws on the same 200, in the order you add contacts. An organisation on a paid plan has its own limit and leaves the shared allowance, which frees its places for your Free organisations. If an organisation goes back to Free, its contacts come back into the allowance: nothing is deleted, but while the total is over 200 you can't add contacts yourself in any of your Free organisations. When all 200 are in use, a new organisation can't be free. Settings → Billing shows how many you have used.

Installation. When it is offered, we can set CRM City up for you, once: your account on one device, your contacts imported, your email and Telegram bot connected, your pipeline set up with three message templates, and a one-hour call on your own data. It is £99, or £79 with Small business or a Custom plan, for one person on one device in one organisation, and £19 for each extra person or device in the same organisation. When you upgrade, tick Add installation on the plan you choose and it is paid with your first payment; that is the only time it is £79. At any other time, on any plan, Buy installation in Settings → Billing sells it on its own, as often as you need it, as a basket with plus and minus on each line: New organisation (£99 each), New team member and New device (£19 each). Team members go up to the seats your plan has (none on Free, which has one user); up to 10 of anything at a time. Each organisation is its own installation, even with the same people. You ask us to carry it out within your 14-day cancellation period, and once it is complete you can no longer cancel it. The installation page lists what it includes and what it does not.

Your price: it stays yours for as long as you stay on that plan — if we raise a plan's price for new subscribers, yours does not move to it. The one thing that can move it is an inflation adjustment, applied in proportion to your own rate, with at least 30 days' notice. Changing plan yourself, in either direction, moves you to that plan's current price.


12.8 The danger zone

At the bottom of Settings, in red, is the ability to reset the organisation's configuration: every module off and the Telegram connection removed, with your data left as it is. It asks for confirmation.

Deleting the whole organisation is not here any more. It is under Settings → Organisation, and it waits 30 days in a bin before anything is removed (12.2).


12.9 What runs on its own

What runs on a schedule, so you know what is happening while nobody is logged in. Times are UTC.

When What
Every 5 minutes Sends scheduled campaigns — held, untouched, while your organisation has no email account of its own connected
Every 5 minutes Retries failed webhook deliveries
Every 5 minutes Sends your day's list to your phone, at the hour you chose in your time zone, and repeats it or brings it back after Snooze the way you set it (3.10). Only to people who turned phone notifications on; never in quiet hours or in Away mode
Every 10 minutes Advances drip sequences — held on their step, untouched, for the same reason
Every hour Sends one summary to someone back from away mode: the tasks that came due, the approval requests answered and the notifications that came in for them while they were away. Once per away period, by email and in the notification bell
Every hour The daily task email: what is due today and what is overdue. Paused: it will come from your own mailbox, once you can connect it, and until then nothing is sent. The same list is on your dashboard, under "Tasks — today and overdue"
Daily, 03:40 Permanently deletes organisations whose 30 days in the bin are over (12.2)
Daily, 06:00 Health check
Daily, 07:00 Creates birthday tasks and fires birthday events; counts meetings and calls you logged ahead of time as contact, once they have happened (a cancelled booking never counts)
Daily, 08:00 Tells a contact whose pause has ended that your messages will resume — held for the same reason
Daily, 09:00 Sends one reminder for an invitation still not accepted three days after it went out — one per invitation, never a second; held for the same reason
Daily, 09:00 Asks a customer for a review after their order is delivered — held for the same reason
Daily, 10:00 Sends one reminder for a review request that got no answer — held for the same reason

A few more run for us alone and never touch a contact: reporting to our own dashboard, the morning summary for our team, and clean-ups. Some of them do nothing until the feature they serve is switched on.

If something you scheduled has not happened, the delay is at most one cycle from this table.


12.10 The one thing to get right

Everything in this chapter is administration. None of it is why you bought the product.

If you do only one thing consistently, make it the thing in chapter 3: look at the dashboard each morning, deal with the longest silence, log what happened offline, and stop when someone turns red.

That habit is worth more than every setting on this page.