An admin does everything a CAM does — read the CAM guide first — and also looks after the queues, the people and the settings. This guide is the extra part. When something is broken, see When something looks wrong.
A normal week
On wide screens, Estimated AI cost and Your tasks sit side by side with matching card heights. On smaller screens, they stack vertically.
- Clear the queues. The dashboard's admin card shows what is waiting in each; Approvals & data quality in the sidebar opens them all. CAMs are often waiting on you — a request left for a week is a client nobody is working.
- Glance at System health on the dashboard. Every row should be green; if one is not, see When something looks wrong.
- Check the alert inbox (the project's own Google account; see Handing 180Connect to a new committee). A failed backup and the weekly notices about client charities and companies changing status arrive there.
- Look at Analytics → Team analytics now and then, for anyone who may need a hand.
The queues
All under Approvals & data quality. Each shows a count; open it to decide.
Approvals
| Queue | What is waiting | What you decide |
|---|---|---|
| Approvals | Changes CAMs suggested to protected client details, and new clients a CAM added by hand | Approve or reject each. Approving a suggested edit applies it to the client straight away |
| Review queue | Replies that could not be matched to a client, records held back before joining the list, and changes to a client's status on the charity or company register | Decide what happens to each. A register change matters most: a charity that has closed, or a company that has been dissolved, should not be contacted |
| Suppress a client | CAMs asking to stop all contact with a client, and every client already blocked | Approve to block all outreach to them. A block can be lifted from the same page |
| Contact information review | Personal contact details that have had no new reply for two years | Keep or remove each, as the branch's data policy asks. Nothing is removed automatically |
| Ownership requests | A CAM asking for a client another CAM owns | Approve to hand the client and its open tasks over, or reject to keep the current owner. The CAM is told either way |
Data quality
| Queue | What is waiting | What you decide |
|---|---|---|
| Possible duplicates | Imported charities that may already be on the client list | Compare the two, then keep one — choosing which details are right — or confirm they are different organisations |
| Data discrepancies | Details where two sources disagree | Choose which value to keep |
| Incomplete records | Clients missing a mission, sector, website, email or city | Fill in what you can find |
Owners
Only an admin can move a client between CAMs directly. Open the client, and on its Ownership card choose Reassign this client (or Assign an owner if nobody has it). Say why in Reason — it is kept on the client's history.
When a CAM leaves, 180Connect hands all their clients over in one go: see A CAM is leaving.
People
Team management in the sidebar.
- Invite a team member to add someone, choosing Admin, CAM or Viewer. A viewer — branch leadership — sees every screen you do and changes nothing.
- Choose someone's name to change their Role, Suspend them, or Reactivate them. Suspending can be undone; Delete account cannot.
- Only email addresses on the domains switched on in Settings → Who can join can be invited.
- Keep at least two admins at all times.
Settings only admins see
In Settings (the account menu), under Platform. These change how the whole branch works, so change them deliberately — and each page lets you change it back.
| Setting | What it controls |
|---|---|
| Score settings | How much each factor counts towards a client's priority score, which orders the client list |
| Data handling rules | Which personal details are removed from imported data before it is saved |
| Restricted fields | Which client details CAMs cannot change directly — they suggest a change, and you approve it in Approvals |
| Outreach sending limit | How many outreach emails the branch sends a day. Raise it slowly: a sudden jump is how Gmail comes to block a mailbox |
| Outreach cycles | The periods the branch's outreach is counted in, for the dashboard and analytics |
| Who can join | The email domains people can be invited from |
Other admin screens
| Screen | What it is for |
|---|---|
| Data imports | Imports from the Charity Commission, Companies House and 360Giving, and the history of every run. See Importing charities |
| Tags | The labels the whole team shares. Add, rename, recolour or delete one here |
| Audit log | Every recorded action, most recent first. It can never be edited or deleted, only added to — the place to answer "who changed this, and when?" |
| Feedback | How the team rates 180Connect. You can ask everyone for a new round |
| Artificial Intelligence | Every email and booklet the AI has written, and what it has cost. See An AI feature says to wait |