How does a product or task become searchable?

Send a copy of the fields you want to search to an index, a collection made for fast lookup. Give each record a stable ID from your source data. For a catalog, you might send product name, description and category, then let shoppers narrow results by category. Your app or a configured connector must send changes and deletions too.

Can two accounts search the same index without seeing each other’s records?

Yes, if the search service enforces each account’s access. Have your server check the signed-in account and issue a short-lived search key restricted to that account’s records and the right index. Give the browser only that scoped key. Keep the parent key used to create it, any unrestricted search keys for private data, and admin and write credentials on the server. A filter the browser can change or remove cannot enforce access.

Only copy the fields the search result needs. Check access again when someone opens the result in your app, and plan how a membership change will affect outstanding search credentials.

How do you verify a private search before indexing customer data?

Start on paper with two fictional accounts and a separate record for each. For a hands-on check, use a disposable Algolia application and test-only records. Verify the exact app ID, index, write connection, search keys and account source before sending any records or searches. If you cannot confirm them, use the paper version.

Check the allowed and excluded results
Give both records the word Cedar. Sign in as each fake account in a fresh browser profile. Inspect the JavaScript files sent to the browser and its Network requests. Confirm none contains an unrestricted, parent, admin or write key for the test application and that search requests use only the short-lived key issued for that account. The actual response should contain only its Cedar record, even without a visible filter selected.
Check that a changed record catches up
Rename one sample item, update the search record and wait for the indexing task to complete. Search for the new text as the allowed account. Delete the sample, wait for the task and confirm the result is gone.
Use the paper fallback when needed
Write which records and fields the search request may return for each fake account. Include what changes when a record is deleted. Mark the live index and credential behavior untested.

What counts toward the bill, and what can you keep?

Algolia’s current standard Free plan lists 10,000 search requests per month and up to 50,000 records. Grow lists 10,000 included monthly requests and 100,000 included records, with usage charges above each allowance. A request is a call to the search service. Search as you type can make several calls for one query someone types.

Keep the source records in your own system. Algolia documents exporting indexed records, settings, rules and synonyms. Save those separately if you need to recreate how results were ranked or filtered.