Assistant permissions and safety

Connecting an assistant is giving software the ability to act as you. That is worth doing carefully, and Drry is built so that doing it carefully is easy.

The permissions, in plain terms

• Know which Drry account you are, and see your name and email. What lets the permission screen and the settings card name the right account.

• Read your communities: their setup and plan, courses, pages, guides, events, automations, audio, the emails you have written, your products (with how many shoppers left checkout without paying in the last 30 days, counts only, never who), offers, tiers and forms, your member list, growth numbers and business numbers such as revenue and engagement (totals only), your community feed including posts held for moderation, who has messaging in your community (counts only) and your own direct messages (never a conversation between members), what is waiting on you, your payment links and sign-only agreements, and your blog with every post, drafts included.

• Create and edit courses, lessons and pages, including ones already published. Publish a course or a lesson, which emails your members. Write, schedule and publish blog posts, which anyone on the internet can read while your blog is on, and whose first publish emails your blog's subscribers when you have that on. Publish an event, which sends its invites, or cancel one, which emails everyone holding it. Make an event public, which opens its own page to anyone with the link, and attach contact lists or all your members as the people it invites: a call that adds an audience saves nothing until it is repeated after you agree. Add pictures from a public address or the picture itself, stored against your storage, to your covers, lessons, guides, blog posts, emails, bio link and page photos, and to your email signature. Post and reply in your community feed as you, which notifies members, and edit or follow what you posted, and reply in your own direct messages, which reaches the people in them at once. Build and rename automations, lay out every step of a journey, and switch one on, which starts it mailing people by itself. A journey can start when a shopper gives their email at your shop checkout and doesn't pay, so a switched-on one can email people who never bought, with what they left and any discount you attach. If you are the owner or an admin, create and change payment links and sign-only agreements, and email a link to the client it names, with reminders. If you own the community, rename your tabs, switch them on or off and set the member menu's order, which members see straight away. Delete a draft that has never reached anyone (a course, guide, page, form, email or journey nobody has seen, used or sent), which cannot be undone. Put people you already have on a list or tag by email address, which can start a journey mailing them, so you are asked first. If you confirm you have permission, import contacts into your audience (under the same plan limits as the console).

• Change your prices, if you own the community: price a membership tier for new members or archive one, create a product and set or change its price, choose which of your saved emails a product's buyers get as their receipt, download or refund email. It never charges anyone, and people already paying keep their rate. An owner or an admin can also create, change and end offers on memberships, event tickets, products and sessions, set the free trial, and set a paid event's ticket price, which strangers are charged from the next checkout. Other staff can put a product on sale or archive it, and set the shop's refund policy.

• Write and rewrite the emails on your Emails page. It never sends a broadcast and never chooses who receives one. It can send a test to your own address, and use Drry's stock photos and pictures you add from a public address or the picture itself. An email already attached to an automation, a form, a booking or a product's receipt or refund will keep sending on its own, so rewriting one changes what those send.

• Stay connected without asking you again each time.

Seeing and removing what is connected

Settings lists every connected assistant, what it was granted, and when. Disconnect ends its access immediately. You can reconnect from inside the assistant whenever you like, which means disconnecting is a cheap thing to do rather than a decision.

Good habits

• Disconnect anything you are not actively using.

• Check the list after somebody leaves your team.

• Ask the assistant to show you what it is about to do on anything that reaches members.

• Remember that an editor's assistant is an editor. Give the seat you would give the person.