What an assistant can do
The full list of what a connected assistant can read and build, what it deliberately cannot touch, and the jobs it is genuinely good at.
- ai
- mcp
- automation
The connector is a fixed set of actions, not open access to your database. Here is all of it.
Reading, with no sign-in
Search this help center.
Read any published help article.
List the sections of the documentation.
Reading your community
List the communities you belong to and open one, and read a community's setup: its plan, its counts, its tab names.
Your courses and the lessons in them, including a lesson's written words and, on a quiz, its questions with the answers marked.
Your guides in full, including every step's words, and the drawer of pieces you have saved to reuse.
Your blog: its settings, its categories and authors, every post in full with its state (drafts included), a post's history and score, and, for the owner and admins on Creator and Growth, your blog's numbers as totals.
Your Resources library, with every file, link and folder, how many times each was downloaded, viewed or opened, and your recent emails about them.
Your audio, your events, your funnel pages, your forms and the audience each one feeds, your products, your offers on memberships, event tickets, products and sessions (and the price in effect on each paid event), and your membership tiers (including whether a free trial is on), and the kinds of session people can book with you.
The full transcript of any audio track or video lesson, including ones you have never published.
How your community looks and what it says.
The emails you have written, the templates and stock photos you can start one from, and what each one did once sent: on plans with analytics, its opens, clicks, the links clicked and what it sold. Your automations in full, including what every step sends.
Your member list: names, handles, seats, when each joined and when they were last seen, and whether their access is paid or free. Email addresses are never included, and the search does not match them either.
Your community feed, a post in full with its replies, one member's seat, activity, access, tags and course progress, the posts held for moderation, and your member growth numbers.
Your own direct messages: your inbox and any one of your conversations, one to one or group, with voice notes read by their transcript. Only conversations you are in, and reading one does not mark it read. It never sees a conversation between two members.
Your payment links, including the client named on each and, for a link with a signed agreement, who has signed it by name (marked if they have not paid yet), your sign-only agreements with the name of each person who signed, and the history of every contact import, which names nobody.
Your email folders, lists, tags and saved segments, with how many people are in each and a segment's rules, but never who is in them. Whether your email goes out from your own domain, and whether it is verified.
Your numbers, on Creator and Growth, for the owner and admins: revenue this month by source and the monthly trend, how many members pay, are trialling or are comped, how engaged your members are, and how your content is doing, down to a course lesson by lesson. Totals only, and no member is named.
What needs you: held posts, open reports, your own unread member conversations, a failed plan payment, and the events coming up today and tomorrow, as counts, plus what to do next in your setup. Each comes with a one-click link that opens the right screen in your console, and works only for you.
Building
Courses. Create a course, add sections and lessons, write a lesson's words, move a lesson, and set when it unlocks: after a number of days, on a date, or once earlier lessons are finished. Set a quiz's questions and its pass mark, and which courses must be finished before this one opens. Publish a course or a lesson, which emails your members, or take a published course or lesson back to a draft.
Resources. Rename and describe the files and links in your members' file library, add a link as a draft, move items between folders, create, rename and reorder folders, and publish or unpublish files. It can email members about published files, which counts toward your send allowance, and limit a file or folder to a membership tier. It cannot upload a file, replace one or set a cover photo, and it cannot delete anything that has been published; do those in the console. See Manage Resources with your assistant.
Blog. Write posts as drafts and edit them, including buttons, cards, tables, embeds and bookmarks, schedule or publish them, take them back down, file them in categories and give them bylines, and set up the blog itself (on or off, its name, kind, address and subscribe band). It cannot upload a picture or cover, start or undo an import, or turn on emailing new posts to your subscribers, and it can only delete a post that was never published. See Manage your blog with your assistant.
Guides. Create one, write its steps, group it into a collection, reorder them, publish it, and share it publicly so anyone with the link and search engines can read it.
Audio. Edit a track's details, publish one, group tracks into collections, and set chapter markers. Correct the words of a transcript, which members read straight away.
Your calendar. Put an event on the calendar as a draft, including one hosted in a Drry video room (Creator) or webinar (Growth), and edit an event. Publish a draft, which sends the invites, the announcement and the reminders (these count toward your send allowance) and cannot be undone. Move a published event, which emails the change to everyone holding it, or cancel one, which emails a cancellation. An event people have paid for is refused, because refunds stay with you. Add the kinds of session people can book, how long each runs, how much notice it needs, and the hours you are bookable.
Funnel pages and forms. Create and edit them, including ones already published, with every section type and option the console offers. Start a page from a template, and use photos from Drry's stock library (never your own uploads). On Growth, write a custom code block. Publish one, which puts it in front of anyone with the link and in front of search engines. It can also change one section at a time, check a page against the page score checklist, take screenshots of it as a visitor would see it (a draft too), list a page's earlier versions, and put one back, which keeps the current page in the history first.
How your community looks. Your brand, your page copy, the questions new members are asked, and the sections on your home and join pages. Rename your tabs and switch the audio, events and Resources tabs on or off, which members see immediately. Rewrite what your new-content and welcome emails and payment receipts say, the postal address in your email footer, and your email signature.
Email. Draft and rewrite the emails on your Emails page, every block and option: the sender name, tracking and header, a template to start from, and stock photos. On a plan with custom code, write custom code blocks. Send a test to your own address only, and take a scheduled email back to a draft. Organise your folders, lists, tags, saved replies and assets, and create saved segments or change their rules, which changes who an unsent email aimed at that segment reaches.
Automations. Create one as a draft, lay out the whole journey with every kind of step (emails, waits, direct messages, tags, lists, a note to you, yes or no branches, splits, waiting for a date or an event, goals and discounted offers, where a community with membership levels names the level each offer discounts), rename it, copy it, and switch it on or off. It can edit a journey that is already on: people already part-way through finish on the version they started, and everyone who enters afterwards gets the new steps. Only the owner can set an offer step's price. Pausing or deleting a journey closes the discount it opened for good. Switching one on starts it mailing the people who meet its trigger, on its own schedule, with nobody watching.
Membership tiers. Add a new rung above the ones a community already has (created with no price, and never the first rung on a community that already charges), set which rung opens a piece of content, and rename a tier. If you own the community it can also price a rung for new members (Growth) and archive one, which stops it being sold and cannot be undone. Everyone already on a rung keeps the rate they joined at.
Products and offers, if you own the community: create a product as a draft with its price, description and download window, and change its name or price. Put a product on sale, take it back to a draft or archive it, and set your shop's refund policy (other staff can do those last three too). Create, change, copy and end offers on memberships, event tickets, shop products and paid sessions (a percent off, an amount off or a new price, for everyone, on a private link, with a code, or both), and switch the free trial for new members on or off, set its length and choose which rungs carry it. Only the owner can create or change an offer or the trial. An owner or admin can also set a paid event's dated price changes (at most five); an early bird below the regular price is an offer, so only the owner can make one. A new price applies to the next checkout, and nobody already paying is repriced.
The community feed and your messages. Post in the feed as you, optionally in a room and optionally emailing members who take email (which counts toward your send allowance, and sends nobody anything if it does not fit), reply to a post or to one reply under it, and pin or unpin a post. In your own direct messages it can reply as you in a conversation you are already in, react to a message and mark a conversation read. It cannot start a new conversation or message anyone new. Staff only, and every post or reply is live at once.
Payment links, if you own the community: create, edit, archive and reactivate one, and email a link to the client it names, from your community, with reminders 1, 3 and 7 days later that stop when they sign or pay.
Agreements to sign, if you own the community and are on Creator or above: create and edit sign-only agreements and their links, and email a link to the client with reminders. An admin can close one, and reopen it on Creator.
Contacts. Import them (under the same plan rules as in the console: up to 100 new contacts in total on the free plan, no such limit from Creator), see the history of every import, and undo one. Using the email addresses you give it, put people you already have on a list or take them off, and give them a tag or take it off. It only ever touches people your community already has: an address it does not hold is reported back, never added. Putting someone on a list that starts a switched-on journey starts mailing them, so it asks you first. It never lists who is on a list or carries a tag.
Deleting drafts. Delete a draft that has never reached anyone: a course, a section or a lesson nobody has opened, a file or link in Resources that was never published, a guide never published, a page no visitor has seen, a form nobody filled in, an email never sent, or a journey never switched on. A deleted draft cannot be brought back, and anything that was ever published, sent or switched on is refused with the reason.
What it cannot do, on purpose
Take or refund money, or change your plan. It can set prices, but it never charges anyone.
Add, remove or comp a member, or change anybody's role.
Send a broadcast, choose who receives one, or list who is on a list, tag or segment.
Read a conversation between members, or start a new conversation. It cannot remove a post either.
See a buyer's address or what they paid. It can see the name of who signed a payment link's agreement, marked if they have not paid.
Approve or remove a held post. It can show you the queue; you decide.
Cancel an event that has sold tickets, or refund one.
Rename a lesson. It can rewrite the words inside one, but not its title.
Upload audio, video or images, or pick one of your own uploads for a page or email that does not already hold it. It can use Drry's stock photos. It cannot generate a transcript.
Delete anything that has ever been published, sent, switched on or used. It can delete a draft nobody has seen, and take a published thing back to a draft.
Join or host a live room, or anything else billed by the minute.
Reach anything your own seat could not reach anyway.
Common questions
Can it read my members' personal data?
Some of it, and it is worth being precise. It can list who is in your community: their name, handle, seat, when they joined, when they were last seen, and whether they pay. It never returns an email address, and its search does not match addresses either, so it cannot be used to ask whether a particular person is a member of yours. It can read your own direct messages, the conversations you are in, but never a conversation between two members. It cannot see who bought what except the name of who signed a payment link's agreement or a sign-only agreement, which is a narrow, named carve-out. Contacts you import are the one direction addresses move, and that import can be undone in one action.
Can it send email to my members?
Not to a list you choose, and it never sends a broadcast. It can email a payment link or an agreement to the one client it names, with reminders, and send a test of an email to your own address. Publishing a course, a lesson, a guide, an audio track or an event emails your members, a post in the feed can email them if you ask, cancelling an event emails the people going, and switching an automation on starts it mailing whoever meets its trigger. Each of those is its own action with its own sentence, never folded into something else, and the permission screen names them.
Will it make things up about my community?
It reads real state through real tools rather than guessing, and the documentation it answers questions from is this help center. Anything it says about your own numbers came from your own community.
Can it work on somebody else's community?
Only communities you belong to, with your own permissions, re-checked on every single action.