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, 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, 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. Post and reply in your community feed as you, which notifies members, 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. If you own the community, create and change payment links and sign-only agreements, and email a link to the client it names, with reminders. Rename your tabs and switch sections on or off, 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, create and change offers on memberships, event tickets, products and sessions, and set the free trial. It never charges anyone, and people already paying keep their rate. Other staff can put a product on sale or archive it, end an offer, 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, never your uploads. An email already attached to an automation, a form or a booking 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.