Contributors
A contributor is another Searchability account you grant write access to one of your lists. It’s how a team collaborates on the same data without sharing an API key: each contributor signs in with their own credentials, works on your list, and can be revoked independently — no shared secret to rotate, no all-or-nothing key to hand around.
Auto-plays · use Back / Next to step through at your own pace.
Add a contributor
- Open the list and choose Options → Add Contributor.
- Type the account name to invite — the box autocompletes as you type.
- Click Add. They can work on the list immediately, with their own login.
What a contributor can and can’t do
Contributors can change the data, but only the owner can change the shape of the list or who has access to it. That split is deliberate: it lets you hand day-to-day content work to a team while you keep the schema and the keys.
| Action | Owner | Contributor |
|---|---|---|
| Add / edit / delete records | Yes | Yes |
| Add new fields | Yes | Yes |
| Rename / remove fields (breaking changes) | Yes | No |
| Delete or transfer the list | Yes | No |
| Manage contributors | Yes | No |
Typical scenarios
- A content team keeps a product catalogue fresh while the platform team owns the schema.
- An external agency loads seasonal data without ever holding the owner’s API key.
- A staging account is granted temporary access during a migration, then revoked when it’s done.
Add and remove contributors from the list’s Options menu in the console, or over the Contributors API. Revocation is immediate for both the console and the API — the moment you remove someone, their access is gone.
A worked example
You own a products list and set its fields once — name and description searchable, price and brand as facets. Your merchandising team needs to keep the catalogue current but must never be able to rename a field and break the storefront. So you add their account as a contributor. They sign in with their own login and add, edit and remove products all day — but the schema stays yours, the API keys stay yours, and if the team changes you revoke the old account and add the new one in seconds, with no key rotation and no downtime.