> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme.md).

# Coming Soon: Registration, Contract Management, CRM and AI Assistant Improvements

We're getting ready to release four sets of improvements: a tidier admin experience for managing registrations and the people in them, a more flexible contracts workflow that lets you manage contracts with anyone (not only funding applicants), a new CRM for managing contacts, lists and bulk emails, and the ability to connect an AI assistant to your Tahua data. Here's an early look at what's coming.

## Registrations: a simpler admin experience

Registrations and the people in them have been reorganised, so it's quicker to find someone and see everything about them in one place.

### A new Registrations menu

The **Users** menu at the top of the screen is now called **Registrations**. It brings applicants, assessors and verifiers (e.g. institutions) together in one list, with **All**, **Applicants**, **Assessors** and **Verifiers** filters. Your organisation's own names for applicants and verifiers are used.

* You can also filter the list by registration type.
* The **State** and **Review Status** columns, and their filters, appear when you're viewing **Applicants** or **Verifiers**. They're hidden when you view **All**.
* **Admins** and **Admin Groups** have moved to the **Settings** menu.

<figure><img src="https://700247708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIjb7z5ij2sBplpwbe1Zs%2Fuploads%2FCDfXGebSCGTE1WdjX0Dc%2Fimage.png?alt=media&amp;token=95302900-3e99-42db-890d-d51c2ab46171" alt=""><figcaption></figcaption></figure>

### One profile page for each person

Each person now has a single profile page, whether they're an applicant, assessor, verifier or a mix. It replaces the separate applicant, assessor and verifier pages, and any old links you've saved will take you to the new page.

* A **Registrations** panel shows every registration the person belongs to, and lets you remove them from one. The remove options depend on the person's role, so you only see the options that apply.
* The page's actions are grouped into **Registration** and **User Actions** panels.
* To add someone to another registration, use **Add to Registration**.

<figure><img src="https://700247708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIjb7z5ij2sBplpwbe1Zs%2Fuploads%2FFyU9mQeWEZj7IMXfex5o%2Fimage.png?alt=media&amp;token=45cdb3dd-6c47-4b7d-b57a-6c26a289ce07" alt=""><figcaption></figcaption></figure>

### The registration page

The registration page now follows the same layout as the profile page:

* The registration's details and actions are combined into a single **Actions** panel.
* For registration types that allow more than one user, a **Users** panel shows everyone linked to the registration. From it you can add a user, accept a request to join, or remove someone from the registration.
* The **Registration** tab, which shows the registration form, is now called **Form**.
* Verifier registrations (e.g. institutions) now use the same registration page as applicants, with their own **Applications**, **Contracts**, **Milestones** and **Letters** tabs.

### Importing verifiers

Verifiers can now be bulk-imported alongside applicants. Use **Import Registrants** on the Registrations list. The template has a sheet for each of your registration types, including your verifier types.

### Safer transfers and deletes

* **Transfer Records** now moves an applicant's access to funding rounds too, such as private round invitations. Before you confirm, it shows any **live** funding rounds the applicant has access to.
* **Delete** warns you when the applicant has access to a live funding round. If the registration is a duplicate, it suggests transferring its records first.
* Tahua now stops a person from ending up with two Individual registrations when you add them to a registration or grant them a role.

## Contracts: manage contracts with any counterparty

Contracts in Tahua now start with the **counterparty**: the organisation or person the contract is with. Linking an application is optional, so you can use the contracts module as a general contract management system, for funded projects and for your other agreements.

### Choose the counterparty first

When you create a contract, you choose the counterparty. You can select an existing registration, or add a new one directly from the contract.

* **If you link an application,** its applicant becomes the counterparty, and its details and milestones are pulled through, as they are today.
* **If you don't link an application,** the contract stands on its own with the counterparty you choose.
* **If you add a new counterparty,** they aren't invited to Tahua straight away. Tick **Invite them to the system when the contract is sent** if you'd like them invited when you send the contract.
* **The counterparty can be different from the linked application's applicant.** Tahua warns you when this happens. Only the counterparty can access the contract; the application's applicant can't.
* **Contract variations** can have a different counterparty from the original contract.

On contract screens, the wording now says **Counterparty** instead of "applicant". On milestone and payment screens, the related column now says **Registration**. In contract templates, the **Applicant Signature Block** personalisation is now called the **Counterparty Signature Block**. Existing templates that use the old personalisation keep working. In the personalisations menu, the **Applicant** category is now called **Registration**.

If your organisation uses a different name for applicants, contract screens will say "Counterparty" by default. Get in touch if you'd like to use a different term.

### Contracts with institutions, without the extra step

You can choose a verifier (e.g. an institution) as the counterparty directly, so you no longer need to tick **"This Contract is with the Institution only"** when setting up the contract.

### Organisation-supplied milestones

Contracts often include things *your* organisation owes the counterparty, such as reports, resources, training or payments due back to you. Turn on **Enable \[your organisation]-supplied milestones** in **Settings > Organisation** (in the Milestones section). Each contract milestone can then be marked as supplied by:

* **The counterparty** (the default): completed by the counterparty in their portal, as today
* **Your organisation**: an internal milestone, completed and submitted by your admins, and reviewed using the usual milestone review process

Milestones supplied by your organisation never appear in the counterparty's portal, and the counterparty isn't notified about them. Payments on these milestones are tracked as **incoming**, money owed to you, and show an **Incoming** label. They aren't synced to your accounting system as bills, and they're excluded from bank payment files. The milestones show a **Supplied by us** label in the admin milestones list.

### Contract expiry reminders

A new **Contract Expiry** email reminder, under **Settings > Emails**, warns you before a contract ends:

* **Recipients:** send it to the contract's **Contract Manager**, or to **Admins** who have access to the contract's funding round.
* **Timing:** choose how many days, weeks or months before the contract end date it's sent.
* **Categories:** optionally limit it to particular contract categories.

Reminders are sent for active contracts (signed by your organisation) that have an end date. Each reminder is sent once per contract. If a contract has a variation, the variation's end date is used. You can edit the email fully, with personalisations such as the contract title, contract manager and contract dates.

### Contracts-only setups

For organisations that use Tahua mainly for contract management, the applications and assessments areas can now be switched off. Menus, lists, reports and settings then only show what's relevant. This is set up by our team, so talk to us if it would suit your organisation.

## CRM: contacts, lists and bulk emails

A new **CRM** module gives you one place to keep track of everyone your organisation works with, including people who don't need to sign in to Tahua, group them into lists, and email them in bulk.

### Contacts: one directory of everyone you work with

A new **CRM** section in the admin menu brings together **Contacts**, **Lists / Segments** and **Bulk Emails**.

#### Everyone is already there

Every person who uses Tahua automatically has a contact, so your directory is ready the day the CRM is switched on. Contact details such as name, email, phone number and title stay up to date with their Tahua account.

You can also add **contacts who don't use Tahua**, such as community members, partners and other stakeholders, without giving them a login. Add them one at a time, or **import them from a CSV file**, with a preview before anything is saved. Re-importing updates existing contacts rather than creating duplicates.

#### Everything about a person in one place

Each contact shows:

* their details, notes and **tags**
* the **organisations** they belong to, kept in sync with their Tahua registrations
* their **roles** in Tahua (applicant, assessor, verifier or admin), with links through to each one
* the **contact lists** they're on
* **internal comments**, shared with their user profile

People's user profiles gain a matching **Contact** tab, so you can see their contact record without leaving the page.

#### Find people quickly

The Contacts list can be searched by name, email or organisation, and filtered by list, tag, organisation or role. You choose which columns to show. Contacts who don't have a Tahua login are clearly marked.

### Lists / Segments

Group contacts into named **lists**, such as a newsletter list, a regional network or past grant recipients. You can add people:

* from their contact page;
* **in bulk** from the Contacts list: select contacts, or select everyone matching your search and filters, then add them to a list or apply a tag;
* **straight from the Applications list**: select applications (for example, everyone in a funding round) and add the applicants to a list.

### Bulk Emails

Send an email to a list, a tag or a hand-picked group in three steps:

1. **Details:** write your email, or start from a saved template. Templates are managed under **Settings > Templates > Bulk Emails**.
2. **Contacts:** choose who receives it, using lists, tags or search.
3. **Send:** review the summary and **send yourself a preview** first. After you click send, you have **60 seconds to undo** before it goes out.

Once sent, you can see the delivery status for each recipient.

{% hint style="info" %}
**Send limits.** To protect email deliverability for everyone, bulk emails have a limit of 2,000 emails per day and 10,000 per month. The Send step shows how many you have left. If you need more, you can request an increase from that screen. Everyday emails such as password resets and letters of offer aren't affected.
{% endhint %}

### Your own fields on contacts

Add your own **custom fields** to contacts under **Settings > Custom Fields**, and show any of them as columns on the Contacts list. As well as the usual text, date, currency and dropdown fields, you can add:

* **File fields** for documents held against a contact, stored securely and downloadable only by admins with access to contacts;
* **Contact link fields** to record relationships between people, such as a parent and their children, or a grantee and their case worker. The relationship shows on both people's contact pages.

#### Let people keep their own details up to date

Registration form questions can be linked to contact fields. When a registration is approved, the answers are copied into the person's contact record, and they're updated again whenever the registration is edited. That means applicants keep their own contact details current just by keeping their registration up to date.

### Reporting and access

* A new **Contacts** data source in Data Reports, including your custom fields
* Contacts are available through the Tahua API
* New admin permissions for the CRM: **Access Contacts**, **Edit Contacts**, **Delete Contacts**, **Manage Contact Lists** and **Send Bulk Emails**, so you control who can see contacts and who can email them

{% hint style="info" %}
**The CRM is off by default.** The CRM, and access to it, will be turned off for every organisation when it's released. If your organisation would like to use it, contact our support team and we'll switch it on for you. Because contacts are created automatically in the background, your directory will already be populated when it's switched on.
{% endhint %}

## AI assistants: ask questions about your Tahua data

You'll be able to connect an AI assistant such as Claude, Cursor or VS Code to Tahua, and ask questions about your data in plain language. For example:

* "Which applications in the Community Fund are still waiting on assessments?"
* "Summarise the funding decisions made this month."
* "Which milestones are overdue, and what payments are outstanding?"

This uses MCP (Model Context Protocol), an open standard supported by a growing number of AI apps.

### Secure, read-only access

* **Read-only.** The assistant can look up and summarise information, but it can never create, change or delete anything in Tahua.
* **Each administrator connects individually.** Connecting always means signing in to Tahua and approving access in your browser. The assistant only sees what that administrator can see under your organisation's data policies.
* **Sensitive details are excluded.** Uploaded files, generated documents such as contracts and letters, bank account details and accounting system identifiers are never shared.
* **Form answers are optional.** By default the assistant works from summary information only. You can turn on the **Form answers** setting to let it read application, registration, report and assessment responses.

### Set up and managed by you

Access is off until you switch it on. Only an administrator with the **Manage Integrations** permission can turn on **Hosted MCP access**, connect AI apps, and see and revoke every connection, all from the **API & MCP** tab in **Settings > Organisation** (previously called **API Access**). Switching access off revokes all connections straight away.

Read more in [AI Assistant Access (MCP)](https://help.tahua.io/knowledge-base/integrations-help-guides/ai-assistant-access).

## When can I use these?

These improvements will be released early next week. We'll let you know when they're live and update the relevant help articles. If you have any questions in the meantime, get in touch with our support team.
