Every action in Lawyer Rebrand

List the chatbots in your organization with their status (draft, live or paused).

chatbots.bot.list · scope chatbots:read · Any member

Show one chatbot's settings: greeting, instructions, lead email, fallback, allowed websites and status.

chatbots.bot.get · scope chatbots:read · Any member

Create a new chatbot as a draft. Pick what it is for (sales, scheduling, support, recruiting or generic); a blank greeting or instructions start from that purpose's suggested wording. Turn it live later by updating its status.

chatbots.bot.create · scope chatbots:write · Any member

Change a chatbot's settings. Only the fields you send change. Status "live" turns the chatbot on for the websites it is installed on; "paused" turns it off.

chatbots.bot.update · scope chatbots:write · Any member

Replace a chatbot's private preview link with a new one. Anyone holding the old link loses access to the preview. Returns the new link's path, which opens on your chatbots address.

chatbots.bot.new_preview_link · scope chatbots:write · Any member

Delete a chatbot. It stops answering on every website it is installed on and disappears from your list. Its leads and conversations are kept.

chatbots.bot.delete · scope chatbots:write · Any member

List the saved versions of a chatbot's settings and knowledge, newest first, with what changed in each and who changed it. Use a version's id to restore it.

chatbots.version.list · scope chatbots:read · Any member

Put a chatbot's settings or knowledge back the way they were in an earlier version. Nothing is lost: the restore is saved as a new version, so it can be undone the same way. Restoring settings never changes whether the chatbot is live.

chatbots.version.restore · scope chatbots:write · Any member

List the websites, pages and files a chatbot answers from, with their size and when each was last read. Use a source's id to refresh or remove it.

chatbots.source.list · scope chatbots:read · Any member

Show the text the chatbot learned from one knowledge source (the first 20,000 characters, and whether there is more).

chatbots.source.get · scope chatbots:read · Any member

Read one web page and add its text to what the chatbot knows. The page must be public; pages built entirely in JavaScript can't be read.

chatbots.source.add_page · scope chatbots:write · Any member

Read a website (up to 250 pages, following its sitemap or links) and add it to what the chatbot knows as one source. Menus, headers and footers are kept once. Takes up to a minute.

chatbots.source.crawl_site · scope chatbots:write · Any member

Add a document to what the chatbot knows. Send either the file's text (content, with a name like price-list.md) or the address of a file to download (url). PDFs with real text, HTML and any plain-text format (txt, md, csv, json) work; scanned PDFs have no text to read. Files are limited to 10 MB and the first 60,000 characters are kept. Files can't be refreshed later: add the new version and remove the old one.

chatbots.source.upload_file · scope chatbots:write · Any member

Remove a website, page or file from what a chatbot knows. The chatbot stops using it right away. The previous knowledge stays in the version history and can be restored.

chatbots.source.remove · scope chatbots:write · Any member

Read a website or page source again so the chatbot has its latest content, skipping the same paths as before. Uploaded files can't be refreshed.

chatbots.source.refresh · scope chatbots:write · Any member

List the people your chatbots collected as leads, newest first: name, email or phone, what they were after, and where each stands (new, contacted, won or lost).

chatbots.lead.list · scope chatbots:read · Any member

Move a chatbot lead along: new, contacted, won or lost.

chatbots.lead.set_status · scope chatbots:write · Any member

List the requests your chatbots passed to a person: visitors who asked for help the chatbot couldn't give. Shows open requests unless you ask for resolved ones or all.

chatbots.handoff.list · scope chatbots:read · Any member

Show one handoff request with the visitor's details and the conversation that led to it.

chatbots.handoff.get · scope chatbots:read · Any member

Mark a handoff request as dealt with, so it leaves your open list.

chatbots.handoff.resolve · scope chatbots:write · Any member

For platform staff working the handoff queue: mark any client's handoff request as dealt with, with an optional note. Recorded in the staff activity log.

chatbots.handoff.staff_resolve · scope operations:write · Platform staff

List your satisfaction surveys with their status (active, draft or archived), scale and which one is the default.

reputation.survey.list · scope reputation:read · Any member

Show one survey in full: its question, labels, thank-you wording for each kind of answer, extra questions, email and text wording, and its look.

reputation.survey.get · scope reputation:read · Any member

Create a new survey styled with your brand. Your first survey becomes the default one that invitations use.

reputation.survey.create · scope reputation:write · Any member

Change a survey's name, scale, alert threshold, wording or look. Only the fields you send change; wording and look fields are merged into what is saved. Wording may use {practice}, {first_name}, {provider} and {location}.

reputation.survey.update · scope reputation:write · Any member

Make an archived or draft survey active again, so invitations can use it.

reputation.survey.activate · scope reputation:write · Any member

Archive a survey so no new invitations use it. Surveys already sent can still be answered. The default survey can't be archived.

reputation.survey.archive · scope reputation:write · Any member

Make this survey the default one that invitations, CSV uploads and connected systems use when no survey is named.

reputation.survey.make_default · scope reputation:write · Any member

Make an active copy of a survey, with the same wording and look, to edit separately.

reputation.survey.duplicate · scope reputation:write · Any member

Delete a survey and cancel its invitations that haven't gone out yet. Its responses are kept. The default survey can't be deleted.

reputation.survey.delete · scope reputation:write · Any member

Email the saved version of a survey to your own address so you can see what patients and customers receive. It never goes to anyone else.

reputation.survey.send_test · scope reputation:write · Any member

List the 100 most recent survey invitations with their status (scheduled, sent, answered, skipped, failed or canceled), channel and when they go out.

reputation.invitation.list · scope reputation:read · Any member

Survey one person by email or text. It goes out after your usual delay from the visit, inside your sending hours, unless sendNow is true. Each survey sent costs tokens. People who unsubscribed or were surveyed recently are skipped.

reputation.invitation.send · scope reputation:write · Any member

Schedule a survey for every row of an appointment list in CSV form (up to 5,000 rows). It needs an email or phone column; name, visit date, location and provider columns are used when present. Each survey sent costs tokens.

reputation.invitation.import · scope reputation:write · Any member

Send every survey and reminder that is due right now instead of waiting for the next automatic run. Each survey sent costs tokens; if the wallet runs out, sending pauses until it is topped up.

reputation.invitation.send_due · scope reputation:write · Any member

Cancel a survey that hasn't gone out yet. One that was already sent can't be canceled.

reputation.invitation.cancel · scope reputation:write · Any member

Report a visit the way a booking or records system does, naming the location and provider by name, and the survey is scheduled for it. Sending the same externalId twice never surveys anyone twice. Each survey sent costs tokens.

reputation.visit.report · scope reputation:write · Any member

Show the headline numbers for a period: NPS or average score, responses, surveys sent, response rate, how many were happy, neutral or unhappy, follow-ups waiting and review link clicks, with a weekly trend.

reputation.summary.get · scope reputation:read · Any member

List survey responses, newest first: score, how they felt, comment, answers and follow-up status. Contact details are not included. Use the returned next value as before to get older ones.

reputation.response.list · scope reputation:read · Any member

Show one survey response with its follow-up status and your team's notes on it. Contact details are not included.

reputation.response.get · scope reputation:read · Any member

Open a follow-up on a response, mark it resolved, or clear it, with an optional note that is added to the response's history.

reputation.response.set_follow_up · scope reputation:write · Any member

Add an internal note to a survey response, visible to your team only.

reputation.response.add_note · scope reputation:write · Any member

Delete a survey response. It no longer shows in any list, count, export or report.

reputation.response.delete · scope reputation:write · Any member

List the public reviews in your reviews inbox, newest first, with their rating, text and reply status. Shows up to 200.

reputation.review.list · scope reputation:read · Any member

Add a public review to your reviews inbox by hand, with its rating, text, author and link.

reputation.review.add · scope reputation:write · Any member

Import reviews from CSV text with a header row. Recognized columns: rating, review (or text), author, date, platform, url, id and location. Rows with an id that was imported before are skipped.

reputation.review.import · scope reputation:write · Any member

Save a draft reply to a review, or mark the reply as posted once you have posted it on the review site. This does not post anything for you. An empty reply clears it.

reputation.review.reply · scope reputation:write · Any member

Remove a review from your reviews inbox. It stays on the review site; this only removes it from your list.

reputation.review.delete · scope reputation:write · Any member

List or search the people you've sent surveys to, newest first, 50 at a time, with whether they still receive surveys. To act on one person, look them up by their exact email address.

reputation.contact.list · scope reputation:read · Any member

Stop sending surveys to one person and cancel any of theirs that haven't gone out yet.

reputation.contact.unsubscribe · scope reputation:write · Any member

Turn surveys back on for someone whose surveys were stopped. Only do this if they asked for it.

reputation.contact.resubscribe · scope reputation:write · Any member

Delete a person from your contacts and cancel their surveys that haven't gone out yet. Their past responses are kept.

reputation.contact.delete · scope reputation:write · Any member

Show your Reputation settings: time zone, sending hours, delay after a visit, reminders, how often one person can be surveyed, alert emails, healthcare mode, sender address and custom survey domain.

reputation.settings.get · scope reputation:read · Any member

Change your general Reputation settings. Only the fields you send change. Healthcare mode keeps names, providers and visit details out of every email.

reputation.settings.update · scope reputation:write · Any member

Set the email address surveys are sent from, like feedback@yourpractice.com. Your domain must be verified before it is used; until then surveys come from our standard address with your name. Send an empty address to go back to the standard one.

reputation.settings.set_sender · scope reputation:write · Any member

Use your own web address for survey links, like feedback.yourpractice.com. It must be a subdomain pointed at us in your DNS. Send an empty domain to go back to the standard address.

reputation.settings.set_domain · scope reputation:write · Any member

List your office locations, which surveys, providers, review links and reports can be tied to.

reputation.location.list · scope reputation:read · Any member

Add an office location, so responses and review links can be tied to it.

reputation.location.add · scope reputation:write · Any member

Remove a location and hide its review links. Its past responses keep their history.

reputation.location.remove · scope reputation:write · Any member

List the providers (doctors, staff or agents) that surveys and reports can be tied to.

reputation.provider.list · scope reputation:read · Any member

Add a provider, optionally at one of your locations, so responses can be tied to them.

reputation.provider.add · scope reputation:write · Any member

Remove a provider from your list. Their past responses keep their history.

reputation.provider.remove · scope reputation:write · Any member

List the public review links (Google, Yelp and others) offered to everyone who answers a survey, and whether each is shown.

reputation.review_site.list · scope reputation:read · Any member

Add a link to one of your public review pages. It is offered on every thank-you page, whatever the score. For Google, a Place ID (starting ChIJ) is turned into the write-a-review link.

reputation.review_site.add · scope reputation:write · Any member

Show or hide one review link on the thank-you pages without deleting it.

reputation.review_site.set_active · scope reputation:write · Any member

Delete a review link for good. To take it off the thank-you pages for now, hide it instead.

reputation.review_site.remove · scope reputation:write · Any member

List the keys your booking or records systems use to report visits, with when each was last used. The keys themselves are never shown again.

reputation.api_key.list · scope reputation:read · Any member

Create a key for a booking or records system to report visits so surveys go out automatically. The key is shown only once, in this result: copy it now, because it can't be shown again.

reputation.api_key.create · scope reputation:write · Any member

Revoke a connection key. Anything using it stops working immediately.

reputation.api_key.revoke · scope reputation:write · Any member

Staff only: customer survey domains and sending addresses waiting on our team to finish setting up, oldest first.

reputation.setup.list · scope operations:read · Platform staff

Staff only: check a customer's custom survey domain or sending address again and record the result. Logged to the staff audit.

reputation.setup.recheck · scope operations:write · Platform staff

Staff only: mark a customer's sending address verified when the email provider can't confirm it but a person has. Surveys start coming from it right away. Logged to the staff audit.

reputation.setup.mark_sender_verified · scope operations:write · Platform staff

List every ad campaign in your organization across Google Ads, ChatGPT ads and Microsoft Advertising, with status, daily budget and results (spend, clicks, conversions) over a recent period, plus totals per platform. Money is in millionths of the account currency.

ads.campaign.list · scope ads:read · Any member

Show one ad campaign with its targeting, ad groups, ads and keywords, and its daily results over the last 7, 30 or 90 days.

ads.campaign.get · scope ads:read · Any member

Pause one campaign on its ad platform so it stops spending. Recorded in the change log; if its family asks for status changes, the other members get a proposed change to review.

ads.campaign.pause · scope ads:write · Any member

Resume one paused campaign on its ad platform. It starts spending the client's ad budget again. Refused if it would take the organization over its daily budget limit.

ads.campaign.resume · scope ads:write · Any member

Change one campaign's daily budget on its ad platform. A higher budget can spend more of the client's ad money; refused if it would take the organization over its daily budget limit.

ads.campaign.set_budget · scope ads:write · Any member

Make one editable draft per chosen campaign for Google Ads or Microsoft Advertising, optionally using a saved recipe. Creates nothing on any ad platform: each draft is reviewed and approved first, and every clone is created paused. To have AI rewrite the drafts, use the rewrite action afterward.

ads.campaign.clone · scope ads:write · Any member

List clone drafts, newest first, with their status (draft, waiting for staff approval, approved, created, failed or discarded), any problems, and whether each is ready to approve.

ads.draft.list · scope ads:read · Any member

Show one clone draft in full: name, budget, bidding, targeting, ad groups with ads and keywords, its problems, and what still blocks approving it.

ads.draft.get · scope ads:read · Any member

Change a clone draft. Only the fields you send change; ad groups and negative keywords, when sent, replace the whole list. Any edit sends the draft back to Draft, and it is always saved paused.

ads.draft.update · scope ads:write · Any member

Have AI rewrite a draft's ads and keywords for its new platform, reading the landing page. Costs 1 token, refunded if the rewrite fails. Read every line before approving.

ads.draft.rewrite · scope ads:write · Any member

Have AI rewrite the ads and keywords of up to 50 drafts. Costs 1 token per draft that succeeds; nothing is charged for one that fails.

ads.draft.rewrite_many · scope ads:write · Any member

Approve a draft once it has no problems left, an ad account is chosen, and its budget fits the organization's daily budget limit. Creates nothing yet. Where staff approval is required, it goes to staff instead.

ads.draft.approve · scope ads:write · Any member

Approve up to 200 drafts at once. Each is checked on its own (problems, ad account, daily budget limit); the ones that can't be approved are listed with the reason.

ads.draft.approve_many · scope ads:write · Any member

Create the campaign on its ad platform from an approved draft. It is always created paused, so it spends nothing until someone resumes it, but it changes the live ad account.

ads.draft.create · scope ads:write · Any member

Create campaigns from up to 200 approved drafts on their ad platforms, each paused. Each is checked against the daily budget limit on its own; failures are listed with the reason.

ads.draft.create_many · scope ads:write · Any member

Discard a draft that hasn't been created. Nothing on any ad platform changes.

ads.draft.discard · scope ads:write · Any member

List the saved clone recipes: reusable budget, bidding, naming and targeting rules applied when campaigns are cloned from one platform to another.

ads.recipe.list · scope ads:read · Any member

Show one saved clone recipe with every rule it applies.

ads.recipe.get · scope ads:read · Any member

Create a clone recipe, or change one by sending its id. When changing, only the fields and settings you send change. Recipes go from ChatGPT ads to Google Ads or Microsoft Advertising, or from Google Ads to Microsoft Advertising.

ads.recipe.save · scope ads:write · Any member

Delete a saved clone recipe. Drafts already made with it keep their settings.

ads.recipe.delete · scope ads:write · Any member

List campaign families (a source campaign and its clones) with their member campaigns and, per kind of change, whether a change on one member is proposed to the others (ask) or stays where it was made (off).

ads.family.list · scope ads:read · Any member

Show one campaign family: its members, its off or ask setting per kind of change, and its open and recent proposed changes.

ads.family.get · scope ads:read · Any member

For one kind of change (copy, keywords, status or budget), choose ask, so a change on one member becomes a proposed change for the others to approve, or off, so it stays on the campaign it was made on. Nothing is ever applied to other members automatically.

ads.family.set_sync · scope ads:write · Any member

Pause every member of a campaign family on its ad platform, so none of them spends. Members that are already paused or can't be changed from here are skipped.

ads.family.pause_all · scope ads:write · Any member

Resume every paused member of a campaign family on its ad platform. They start spending the client's ad budget; each is refused if it would go over the daily budget limit.

ads.family.resume_all · scope ads:write · Any member

Take one campaign out of its family, so changes on it are no longer proposed to the others and theirs to it. The campaign itself is unchanged.

ads.family.remove_member · scope ads:write · Any member

List changes proposed between family members, newest first, each with a plain-English summary. Shows open ones unless another status is asked for.

ads.proposal.list · scope ads:read · Any member

Approve one open proposed change: it is applied now to its campaign on the live ad platform. A resume or a budget increase is checked against the daily budget limit first.

ads.proposal.approve · scope ads:write · Any member

Reject one open proposed change. Nothing is applied to any campaign.

ads.proposal.reject · scope ads:write · Any member

List the organization's connected ad accounts (Google Ads, ChatGPT ads, Microsoft Advertising and sample accounts) with their sync status and when each was last brought up to date.

ads.account.list · scope ads:read · Any member

Add three sample ad accounts filled with test campaigns, to try Paid Ads without connecting a real account. They are labeled as samples everywhere and can be disconnected any time. Owners and admins only.

ads.account.add_samples · scope ads:write · Any member

Add a ChatGPT ads account, kept up to date by importing its Ads Manager exports. Owners and admins only.

ads.account.add_chatgpt · scope ads:write · Any member

Read the latest campaigns and results from one ad account now, instead of waiting for the daily sync. Only reads from the platform; ChatGPT ads accounts are kept current by CSV import instead.

ads.account.sync · scope ads:write · Any member

Disconnect an ad account from Paid Ads. Its campaigns stay in the history and nothing on the platform changes. Owners and admins only.

ads.account.disconnect · scope ads:write · Any member

Read a ChatGPT Ads Manager CSV export and show the campaigns and days of results it contains, with any warnings, without saving anything.

ads.account.preview_csv · scope ads:read · Any member

Import a ChatGPT Ads Manager CSV export into a ChatGPT ads account: its campaigns and daily results. Preview it first to check what it contains.

ads.account.import_csv · scope ads:write · Any member

Show the spreadsheet linked for editing drafts (if any), when it was last synced, and its recent syncs with their status.

ads.sheet.get · scope ads:read · Any member

Show one sync of the editing sheet: every change it would make to the drafts, any problems found in the sheet, and, once applied, what changed.

ads.sheet.get_run · scope ads:read · Any member

Link the built-in sample spreadsheet, to try editing drafts from a sheet before linking your own Google Sheet. Owners and admins only.

ads.sheet.link_sample · scope ads:write · Any member

Read the linked sheet and list what it would change in the drafts, as a sync to review. Nothing is applied until the sync is applied.

ads.sheet.sync · scope ads:write · Any member

Apply a reviewed sheet sync: create, update or discard drafts as it lists. Writes drafts only; nothing is approved or created on any ad platform, and every campaign is still created paused.

ads.sheet.apply_run · scope ads:write · Any member

Throw away a sheet sync without applying it. No draft changes.

ads.sheet.discard_run · scope ads:write · Any member

Unlink the spreadsheet used for editing drafts and forget its access. Drafts stay as they are. Owners and admins only.

ads.sheet.unlink · scope ads:write · Any member

The organization's ads report: spend, clicks, conversions and cost per conversion, by platform, campaign family and campaign, for the last 7, 30 or 90 days or a date range. Money is in millionths of the currency.

ads.report.get · scope ads:read · Any member

The organization's Paid Ads setup checklist: for each ad platform, what is needed, where it stands (connected or needs attention, from its real ad accounts) and the next steps.

ads.onboarding.get · scope ads:read · Any member

List the read-only report links made for this organization, with each link's address, range, expiry and views. Owners and admins only.

ads.report_link.list · scope ads:read · Any member

Make a read-only link to this organization's ads report that anyone with the link can open until it expires (90 days at most). Owners and admins only.

ads.report_link.create · scope ads:write · Any member

Revoke a report link. It stops working right away. Owners and admins only.

ads.report_link.revoke · scope ads:write · Any member

Show the organization's daily budget limit across every ad platform (none means no limit) and its no-conversions alert thresholds. Money is in millionths of US dollars.

ads.settings.get · scope ads:read · Any member

Change the organization's daily budget limit (the most every enabled campaign on every platform may spend per day together, in US dollars; null for no limit) or its no-conversions alert. Only the fields you send change. Owners and admins only.

ads.settings.update · scope ads:write · Any member

The Paid Ads change log, newest first: who changed what and when, with before and after, for campaigns, drafts, proposed changes, accounts and settings.

ads.change.list · scope ads:read · Any member

Staff: clone drafts across every client organization that wait for staff approval, and clones a platform refused to create in the last weeks, with each client's name.

ads.ops_draft.list · scope operations:read · Platform staff

Staff: approve a client's clone draft that waits for staff approval (the client can then create it, paused), or send it back to the client as a draft. Checked against the client's daily budget limit.

ads.ops_draft.decide · scope operations:write · Platform staff

Staff: every organization's connected ad accounts, failing ones first, with the client's name, status and last sync.

ads.ops_account.list · scope operations:read · Platform staff

Staff: re-run the sync for one client's ad account now. Only reads from the platform.

ads.ops_account.sync · scope operations:write · Platform staff

Staff: the client organizations onboarded to Paid Ads, with their contact, status (onboarding, active or archived) and partner.

ads.ops_client.list · scope operations:read · Platform staff

Staff: one client's onboarding: contact, status, the ad platforms on its checklist with their ids and link steps, and where each stands.

ads.ops_client.get · scope operations:read · Platform staff

Staff: onboard a client. Creates its organization under the partner (or finds one with that name), records its contact and the ad accounts it uses, and can invite the contact, by email if asked.

ads.ops_client.add · scope operations:write · Platform staff

Staff: make an organization that already exists a Paid Ads client being onboarded. Nothing is created and no one is invited.

ads.ops_client.onboard_existing · scope operations:write · Platform staff

Staff: check a CSV of clients and show what each row would do, with any problems, without importing anything.

ads.ops_client.check_csv · scope operations:read · Platform staff

Staff: onboard every valid row of a clients CSV (500 at most) under one partner, and optionally invite each contact, by email if asked. Nothing imports while the file has problems.

ads.ops_client.import_csv · scope operations:write · Platform staff

Staff: save the contact name and email for a client being onboarded. Only the fields you send change.

ads.ops_client.save_contact · scope operations:write · Platform staff

Staff: mark a client onboarding, active, or archived (archived clients are hidden from the client list).

ads.ops_client.set_status · scope operations:write · Platform staff

Staff: add an ad platform the client uses, with its account id, to the client's setup checklist.

ads.ops_client.add_platform · scope operations:write · Platform staff

Staff: remove one ad platform from a client's setup checklist. Connected ad accounts are not touched.

ads.ops_client.remove_platform · scope operations:write · Platform staff

Staff: mark that a manager-account link request was sent or accepted outside the app, or clear those marks. Connected still comes only from a real ad account connection.

ads.ops_client.record_link_step · scope operations:write · Platform staff

Staff: invite a person to a client's organization as an owner or member, by email if asked (otherwise the invitation link is returned to send yourself).

ads.ops_client.invite · scope operations:write · Platform staff

Staff: send a link request from the agency's manager account to the client's ad account through the ad platform, which notifies the client to accept it. Run from the agency's organization.

ads.ops_client.send_link_request · scope operations:write · Platform staff

Staff: ask the ad platform whether the client accepted the manager-account link request. Run from the agency's organization.

ads.ops_client.check_link · scope operations:write · Platform staff

Staff: add the client's ad accounts reachable through the agency's manager account, only the ids on the client's checklist, to the client's organization. Run from the agency's organization.

ads.ops_client.add_accounts · scope operations:write · Platform staff

Staff: the read-only report links made for one client's organization.

ads.ops_report_link.list · scope operations:read · Platform staff

Staff: make a read-only link to one client's ads report that anyone with the link can open until it expires (90 days at most).

ads.ops_report_link.create · scope operations:write · Platform staff

Staff: revoke one of a client's report links. It stops working right away.

ads.ops_report_link.revoke · scope operations:write · Platform staff

Staff: the Google Ads manager and Microsoft agency accounts connected in your current organization (the agency), with their status. Sign-ins are never shown.

ads.ops_manager.list · scope operations:read · Platform staff

Staff: disconnect one of the agency's manager accounts. Client ad accounts already added keep working until their own sign-in is removed.

ads.ops_manager.disconnect · scope operations:write · Platform staff

Add a website address to My Websites so it can be audited or have work requested on it. Adding one you archived brings it back.

websites.website.add · scope websites:write · Any member

Remove a website from My Websites. Its audits and past requests are kept, and adding the address again restores it.

websites.website.archive · scope websites:write · Any member

List the websites your organization manages (My Websites), with how many open Client Work requests and audits each one has.

websites.website.list · scope websites:read · Any member

Change the label shown for one of My Websites. Send an empty label to clear it.

websites.website.rename · scope websites:write · Any member

Archive a built site so it no longer appears as active. Its history and saved versions are kept.

websites.site.archive · scope websites:write · Any member

Start a new draft site from a template. It gets a free web address made from its slug right away; nothing is published or charged until you publish it.

websites.site.create · scope websites:write · Any member

Show one built site in full: name, address slug, settings, every page and its blocks, status and addresses.

websites.site.get · scope websites:read · Any member

List the sites built with the website builder in your organization, with status (draft, published, archived) and addresses.

websites.site.list · scope websites:read · Any member

List the starter templates a new site can be built from, with their kinds and design variants.

websites.template.list · scope websites:read · Any member

List a site's publish history, newest first: when each version went live, who published it, and what changed.

websites.site_version.list · scope websites:read · Any member

Publish a site so visitors see its current pages, and save this version to its history. Each publish spends tokens from your balance.

websites.site.publish · scope websites:write · Any member

Bring back an earlier published version of a site. Mode draft loads it into the editor for review (only while the site is a draft); mode publish restores it and publishes it now, which spends tokens like any publish.

websites.site_version.restore · scope websites:write · Any member

Take a published site offline and return it to draft. Publishing it again later spends tokens again.

websites.site.unpublish · scope websites:write · Any member

Change a site's name, address slug, settings or pages. Only the fields you send change; pages replaces the whole page list. Edits to a published site show to visitors right away.

websites.site.update · scope websites:write · Any member

Connect a domain you own to a site. Spends tokens from your balance. Returns two DNS records to add at your domain provider: a TXT record proving you own it and a record pointing it at the site.

websites.domain.add · scope websites:write · Any member

Look up a custom domain's DNS records again, the same as the Check now button. Marks ownership verified and the domain live once its records are found.

websites.domain.check · scope websites:write · Any member

List the web addresses attached to a site: its free address and any custom domains, with whether each is live, ownership-verified, and the DNS records still needed.

websites.domain.list · scope websites:read · Any member

Make a verified, live domain the site's main address. The domain must already show as active.

websites.domain.make_primary · scope websites:write · Any member

Disconnect a domain from a site. Visitors to that address stop seeing the site.

websites.domain.remove · scope websites:write · Any member

Add one or more items of work to one of your requests, each with the page it applies to if you know it.

websites.request_item.add · scope websites:write · Any member

Approve the finished work on a request that is ready for your review. This bills the completed hours and fixed-price items in tokens and closes the request. The team is emailed.

websites.request.approve_completion · scope websites:write · Any member

Approve the itemized list the team sent so work can start. This authorizes the work: when it is done and you approve it, the hours are billed in tokens. The team is emailed.

websites.request.approve_scope · scope websites:write · Any member

Upload a file, such as a photo or a document, to one of your requests or to one item of it.

websites.request.attach_file · scope websites:write · Any member

Cancel one of your open requests. Nothing more is done on it and nothing is billed for it.

websites.request.cancel · scope websites:write · Any member

Post a message on one of your requests, or on one item of it. The team and the other people following the request are emailed.

websites.request.comment · scope websites:write · Any member

Open a website request from one of your audit reports, with the findings to fix as items. The team is emailed. Nothing is charged until you approve the list and the finished work.

websites.request.create_from_audit · scope websites:write · Any member

Ask the team for work, optionally with a list of items. The team is emailed. Nothing is charged until you approve the list and then approve the finished work.

websites.request.create · scope websites:write · Any member

Turn down one proposed item of work on your request so it is left out of the approved list.

websites.request_item.decline · scope websites:write · Any member

Show one Client Work request: its status, each item of work with estimated and actual hours, the message thread, attached files and the hourly rate in tokens.

websites.request.get · scope websites:read · Any member

List your organization's Client Work requests (website, Google Business Profile, social, content and other work), newest first, with their status.

websites.request.list · scope websites:read · Any member

Stop, or start again, getting emails about one request. Your other requests are not affected.

websites.request.mute · scope websites:write · Any member

Start a follow-up request linked to a completed one, keeping the original and its history. Everyone following it is emailed.

websites.request.reopen · scope websites:write · Any member

Instead of approving finished work, say what still needs doing. The request goes back to in progress at no charge and the team is emailed.

websites.request.request_changes · scope websites:write · Any member

Record the page or place on your site an item of work applies to, like a full address or 'the footer'.

websites.request_item.set_page · scope websites:write · Any member

Staff: make a team member the owner of a request. They are emailed.

websites.ops_request.assign · scope operations:write · Platform staff

Staff: open a Client Work request for a client organization, optionally with a list of items. The team is emailed. Nothing is billed until the client approves the list and the finished work.

websites.ops_request.create · scope operations:write · Platform staff

Staff: show one Client Work request with its items, the whole thread including team-only notes, and attached files.

websites.ops_request.get · scope operations:read · Platform staff

Staff: list client organizations work can be opened for, with their partner, optionally filtered by name.

websites.ops_client.list · scope operations:read · Platform staff

Staff: list Client Work requests across every client, oldest first, with each client and partner name.

websites.ops_request.list · scope operations:read · Platform staff

Staff: send a request's finished list of items to the client and ask them to approve it. The client is emailed.

websites.ops_request.send_scope · scope operations:write · Platform staff

Staff: change a request's priority (low, normal, high) or due date. Send a null due date to clear it.

websites.ops_request.set_details · scope operations:write · Platform staff

Staff: add an item of work to a request, billed by the hour (with an estimate) or at a fixed price in tokens. The client is emailed.

websites.ops_request_item.add · scope operations:write · Platform staff

Staff: upload a file to a client's request or to one item of it.

websites.ops_request.attach_file · scope operations:write · Platform staff

Staff: reply to the client on a request or one item of it, which emails them, or leave a team-only note the client never sees.

websites.ops_request.comment · scope operations:write · Platform staff

Staff: start a follow-up request linked to a completed one. Everyone following it, including the client, is emailed.

websites.ops_request.reopen · scope operations:write · Platform staff

Staff: change an item's status, estimated hours, actual hours worked or the page it applies to. Only the fields you send change.

websites.ops_request_item.update · scope operations:write · Platform staff

Staff: start work on a request whose list the client approved. It moves to in progress.

websites.ops_request.start_work · scope operations:write · Platform staff

Staff: tell the client the work is done and ask them to check and approve it. The client is emailed.

websites.ops_request.submit_for_review · scope operations:write · Platform staff

Show how you get Client Work emails: right away, as a daily digest, or not at all, which kinds are switched off, and which requests you muted.

websites.notification_settings.get · scope websites:read · Any member

List your recent Client Work notifications, newest first, with which ones are unread.

websites.notification.list · scope websites:read · Any member

Mark one notification as read, or all of your unread notifications when no id is given.

websites.notification.mark_read · scope websites:write · Any member

Change how you get Client Work emails (right away, a daily digest, or off) and switch individual kinds on or off. Only what you send changes.

websites.notification_settings.update · scope websites:write · Any member

List the kinds of website audit you can run (accessibility, performance, search, AI chatbots), whether each has a deep version, and roughly how many tokens each costs.

audit.category.list · scope audit:read · Any member

List your organization's 50 most recent website audits with their type, status and when they finished.

audit.run.list · scope audit:read · Any member

Show one audit: whether it is queued, running, finished or failed, and each check's score and summary once it is done.

audit.run.get · scope audit:read · Any member

Start an audit of a web address. Spends tokens from your balance (about 30 to 50 a run, twice that for a deep audit). The audit is queued and usually finishes within minutes.

audit.run.start · scope audit:write · Any member

List the websites your organization audits, with their labels.

audit.site.list · scope audit:read · Any member

Show which audits run automatically for one website, how often (weekly or monthly), and when each runs next.

audit.site.get_schedules · scope audit:read · Any member

Add a website to your organization so it can be audited and scheduled. Adding an address you deleted brings it back.

audit.site.add · scope audit:write · Any member

Turn automatic audits on or off for one website, per type, weekly or monthly. Each scheduled audit spends tokens when it runs. Types you leave out keep their current schedule.

audit.site.set_schedules · scope audit:write · Any member

Remove a website from your audited websites and stop its scheduled audits. Past reports are kept and it can be restored.

audit.site.delete · scope audit:write · Any member

Bring back a website you deleted from your audited websites.

audit.site.restore · scope audit:write · Any member

Ask the team for a quote to fix the problems an audit found on a website. The team is emailed, and so are you, with a confirmation.

audit.remediation.request · scope audit:write · Any member

Staff: list requests to fix websites from every partner, newest first, with contact details and status. Open ones by default.

audit.ops_remediation.list · scope operations:read · Platform staff

Staff: move a request to fix a website along the pipeline: new, contacted, quoted, won or lost.

audit.ops_remediation.set_status · scope operations:write · Platform staff

List your cold email campaigns with their status (draft, active, paused, completed or archived), whether test mode is on, and headline numbers: sent, opened, replied and bounced.

coldemail.campaign.list · scope coldemail:read · Any member

Show one campaign in full: its schedule and sending limits, which inboxes send it, tracking settings, every step of the sequence with its other versions, and its numbers.

coldemail.campaign.get · scope coldemail:read · Any member

Create a new cold email campaign as a draft. Nothing sends until it has steps, inboxes and recipients and you launch it.

coldemail.campaign.create · scope coldemail:write · Any member

Change a campaign's name, schedule, sending limits, tracking or which inboxes send it. Only the fields you send change. To start or stop sending, use launch, pause or end instead.

coldemail.campaign.update · scope coldemail:write · Any member

Start sending a draft campaign, or resume a paused one (this clears an automatic pause). Emails go out to its recipients within the sending window and each one costs tokens; in test mode only your test recipients are mailed.

coldemail.campaign.launch · scope coldemail:write · Any member

Stop an active campaign from sending. Recipients keep their place, so resuming carries on where it left off.

coldemail.campaign.pause · scope coldemail:write · Any member

Mark a campaign completed or archived. It stops sending for good; its results stay.

coldemail.campaign.end · scope coldemail:write · Any member

While test mode is on, a campaign only emails your test recipients (set in Settings). Turning it off on an active campaign starts emailing its real recipients.

coldemail.campaign.set_test_mode · scope coldemail:write · Any member

Delete a campaign with its steps, recipients and results. This can't be undone; archiving keeps the results.

coldemail.campaign.delete · scope coldemail:write · Any member

Create a follow-up campaign that starts for each person whose reply in this campaign is marked with the chosen category. It copies the schedule, inboxes and test mode, and sends nothing until you add its first step.

coldemail.campaign.create_follow_up · scope coldemail:write · Any member

Add an email to a campaign's sequence. Leave out the position to add it at the end. The change is saved in the sequence history.

coldemail.step.add · scope coldemail:write · Any member

Change one step of a campaign's sequence: its wording, subject, wait or position. Only the fields you send change, and the next emails use the new text.

coldemail.step.update · scope coldemail:write · Any member

Remove one step (and its other versions) from a campaign's sequence. The sequence history keeps the old version so it can be restored.

coldemail.step.delete · scope coldemail:write · Any member

Add another version (B, C and so on) of a step to test against the original. Each recipient gets one version, chosen by weight.

coldemail.step_version.add · scope coldemail:write · Any member

Change version B, C and so on of a step. Only the fields you send change. Weight 0 pauses that version.

coldemail.step_version.update · scope coldemail:write · Any member

Remove one extra version (B, C and so on) of a step. The sequence history keeps it so it can be restored.

coldemail.step_version.delete · scope coldemail:write · Any member

Write a campaign's emails with AI from a short brief, using your company profile. Costs 1 token. The steps are added after any existing ones, or replace them if asked and nothing has been sent yet. Read and edit them before launching.

coldemail.sequence.write_ai · scope coldemail:write · Any member

List the saved versions of a campaign's sequence, newest first, with what changed in each and who changed it.

coldemail.sequence.history · scope coldemail:read · Any member

Put an earlier saved version of a campaign's sequence back. Emails already sent and people partway through keep their place; the next emails use the restored text. Refused if it would remove a step that has already been sent.

coldemail.sequence.restore · scope coldemail:write · Any member

List the people in a campaign with their status, reply category and current step. Page with the next value returned.

coldemail.recipient.list · scope coldemail:read · Any member

Add up to 5,000 people to a campaign. Each is checked first: your blocklist, the global bounce and spam-report lists, do not contact, disposable addresses and domains that can't receive mail are skipped. If the campaign is running, they start receiving its emails.

coldemail.recipient.add · scope coldemail:write · Any member

Add people to a campaign from CSV text with a header row (up to 25,000 rows), with the same checks as adding them one by one. Columns are matched by their headers unless you say which column is which. If the campaign is running, they start receiving its emails.

coldemail.recipient.import_csv · scope coldemail:write · Any member

List the inboxes that send your cold email, with their daily limit, warmup, status (and why one is paused), how replies are read, and the inbox groups. Passwords and keys are never shown.

coldemail.inbox.list · scope coldemail:read · Any member

Show one inbox in full, including its latest DNS check, blocklist check and inbox placement tests. Passwords and keys are never shown.

coldemail.inbox.get · scope coldemail:read · Any member

Connect a mailbox to send from, either your own mailbox over SMTP (with IMAP to read replies) or a SendGrid sender. Google and Microsoft sign-in has to be done on the Inboxes page. The password or key is stored encrypted.

coldemail.inbox.add · scope coldemail:write · Any member

Change the most emails an inbox sends a day: up to 500 for a mailbox, 10,000 for a SendGrid sender. Warmup still ramps a new inbox up to it.

coldemail.inbox.set_daily_limit · scope coldemail:write · Any member

Add or replace the SendGrid API key a SendGrid inbox sends with, and connect its delivery reports. The key is stored encrypted.

coldemail.inbox.set_sendgrid_key · scope coldemail:write · Any member

Choose how replies to an inbox are picked up: imap reads the mailbox (any provider; Gmail and Outlook need an app password), parse uses a reply subdomain you point at SendGrid, and none turns reply tracking off.

coldemail.inbox.set_reply_settings · scope coldemail:write · Any member

Disconnect and remove an inbox. Campaigns stop sending from it.

coldemail.inbox.delete · scope coldemail:write · Any member

Send one real email from an inbox to your own address, through the same route a campaign uses, to prove it can send. It only ever goes to you, isn't billed, and a failure shows the provider's own reason.

coldemail.inbox.send_test · scope coldemail:write · Any member

Check the inbox's domain for SPF, DKIM, DMARC and mail records now, with plain fixes for anything missing. The result is saved on the inbox.

coldemail.inbox.check_dns · scope coldemail:write · Any member

Check the inbox's sending, reply and tracking domains against the main domain blocklists now. The result is saved on the inbox.

coldemail.inbox.check_blocklists · scope coldemail:write · Any member

Send one test email from an inbox to our test mailboxes at the major providers and report whether it lands in the inbox, promotions or spam (results within about 30 minutes). Costs 1 token.

coldemail.inbox.placement_test · scope coldemail:write · Any member

Turn a paused inbox back on (it pauses itself after repeated failed sends or a blocklist listing). Its active campaigns start emailing their recipients again; if the cause isn't fixed, it pauses again.

coldemail.inbox.resume · scope coldemail:write · Any member

Create an inbox group (leave out the id) or change one: its name and which inboxes are in it. A campaign can send from a whole group.

coldemail.inbox_group.save · scope coldemail:write · Any member

Delete an inbox group. Campaigns that used it keep their individually chosen inboxes.

coldemail.inbox_group.delete · scope coldemail:write · Any member

Show your Cold Email settings: the business mailing address on every email, test recipients, the company profile used for AI writing, sending domains and their DNS records, the tracking domain, whether a booking link is set, and how many entries the blocklist has.

coldemail.settings.get · scope coldemail:read · Any member

Set the physical mailing address that the law requires at the bottom of every commercial email. Nothing sends until it is set.

coldemail.settings.set_postal_address · scope coldemail:write · Any member

Add an address that campaigns in test mode send to. In test mode, only these addresses are emailed.

coldemail.test_recipient.add · scope coldemail:write · Any member

Stop sending test-mode emails to an address.

coldemail.test_recipient.remove · scope coldemail:write · Any member

List your do-not-mail list, newest first: addresses and whole domains, and where each came from (added by your team, an unsubscribe, an opt-out reply, a complaint or a bounce).

coldemail.blocklist.list · scope coldemail:read · Any member

Add email addresses or whole domains (like competitor.com) to your do-not-mail list. No campaign emails them again.

coldemail.blocklist.add · scope coldemail:write · Any member

Remove an entry your team added to the blocklist, so campaigns can email it again. Unsubscribes, opt-out replies, complaints and bounces can't be removed.

coldemail.blocklist.remove · scope coldemail:write · Any member

Change what AI writing knows about your company: what you do, your offer, answers to common questions, your signature and your booking link (used for {{booking_link}}). Only the fields you send change.

coldemail.profile.update · scope coldemail:write · Any member

Create the webhook address your booking tool (Calendly, Cal.com) calls when someone books, so their sequence stops and they are marked meeting booked. Replacing it stops the old address working at once.

coldemail.booking_link.reset · scope coldemail:write · Any member

Add a domain you send from, to prove you own it. Returns a TXT record to add at your DNS provider; then run the check. Needed when your inboxes send through a shared delivery account.

coldemail.sending_domain.add · scope coldemail:write · Any member

Look up a sending domain's TXT record now and mark it verified if it matches. DNS changes can take up to an hour to appear.

coldemail.sending_domain.check · scope coldemail:write · Any member

Remove a sending domain. Inboxes sending from it through a shared delivery account stop until it is verified again.

coldemail.sending_domain.remove · scope coldemail:write · Any member

Use your own subdomain (like track.yourdomain.com) for open and click tracking. Returns the CNAME record to add; then run the check. Our team connects it once it resolves.

coldemail.tracking_domain.set · scope coldemail:write · Any member

Look up the tracking domain's CNAME record now. DNS changes can take up to an hour to appear.

coldemail.tracking_domain.check · scope coldemail:write · Any member

Stop using your custom tracking domain. Tracked links go back to the standard address.

coldemail.tracking_domain.remove · scope coldemail:write · Any member

List replies from recipients, newest first, with the person, the campaign and the category. Out-of-office and bounce notices are left out unless you ask for them.

coldemail.reply.list · scope coldemail:read · Any member

Show one recipient's whole conversation: every email sent and received, team notes, any saved reply draft, and whether it is snoozed or archived.

coldemail.conversation.get · scope coldemail:read · Any member

Correct how a reply is categorized; your choice wins over the automatic one. It takes effect at once: do not contact blocks the person in every campaign, interested and similar categories can start a follow-up campaign that emails them, and out of office lets the sequence carry on.

coldemail.reply.set_category · scope coldemail:write · Any member

Send a reply in a conversation from the inbox it went out from, in the same email thread, quoting their message. Not billed. Refused for anyone who opted out or is on a do-not-mail list.

coldemail.conversation.send_reply · scope coldemail:write · Any member

Write a suggested reply with AI from the conversation and your company profile. Costs 1 token. The draft is saved on the conversation; nothing is sent.

coldemail.conversation.draft_reply · scope coldemail:write · Any member

Throw away the reply draft saved on a conversation.

coldemail.conversation.discard_draft · scope coldemail:write · Any member

Hide a conversation from the inbox until a set time. It comes back then, or sooner if they write again.

coldemail.conversation.snooze · scope coldemail:write · Any member

Archive a conversation, move it back to the inbox, end a snooze, or mark its latest reply unread.

coldemail.conversation.set_state · scope coldemail:write · Any member

Add a private note to a conversation. Only your team sees it; it is never sent.

coldemail.conversation.add_note · scope coldemail:write · Any member

Add or remove tags on the contact behind a conversation, so you can find or import them later.

coldemail.conversation.tag · scope coldemail:write · Any member

Mark up to 150 conversations read, archive or unarchive them, or set the category of each one's latest reply (which takes effect as it would one at a time, including follow-up campaigns that email them).

coldemail.conversation.bulk_update · scope coldemail:write · Any member

List your organization's contacts, newest first, with their tags and whether they are marked do not contact. Filter by tag or search by name, email or company.

coldemail.contact.list · scope coldemail:read · Any member

Add tags to up to 200 contacts, for example to import them into a LinkedIn campaign later.

coldemail.contact.add_tags · scope coldemail:write · Any member

Remove tags from up to 200 contacts.

coldemail.contact.remove_tags · scope coldemail:write · Any member

Mark up to 200 contacts do not contact across your whole organization. Their campaigns stop now, and no Cold Email or LinkedIn campaign reaches them again.

coldemail.contact.mark_do_not_contact · scope coldemail:write · Any member

Undo a mistaken do-not-contact mark on up to 200 contacts. No campaign restarts; add them to a campaign again to reach them.

coldemail.contact.clear_do_not_contact · scope coldemail:write · Any member

List the private, read-only report links you share with clients, the campaigns each shows, and when each was last viewed.

coldemail.client_report.list · scope coldemail:read · Any member

Create a private, read-only link showing chosen campaigns' results, to send to a client. Anyone with the link can view it until you revoke it.

coldemail.client_report.create · scope coldemail:write · Any member

Change which campaigns a client report shows, or whether it shows replies. Only the fields you send change.