Manage your blog with your assistant

If you have connected Drry to Claude or ChatGPT, it can work on your blog the way you can in the console, with your own permissions. A post it creates is always a draft nobody can see, so you can look at it before anyone else does. See Connect Claude or ChatGPT.

What it can do

• Read your blog's settings and every post with its state, or one post in full, and search your posts.

• Write. Start a post, optionally from one of your templates, and write its title, subtitle, excerpt, search text and whole body, including columns, @ mentions of your courses, lessons, events, audio tracks, offers, other posts and other items, buttons, cards for your courses, lessons, events, products, audio tracks, offers and other posts, embeds, tables, bookmarks, and funnel sections such as a booking, an offer or a form. It can set a post's link, feature a post, and place the members-only line.

• Pictures. Add a picture to a post from a public address or the picture itself, and use it as an Image block, a Gallery photo or the post's cover, or set a guest author's or teammate's photo. A picture is a JPEG, PNG, WebP or GIF and counts toward your storage. One it adds and never uses in a post is removed after a day. A post with no cover shows the first picture in its free part on cards and link previews, as it does when you write it yourself.

• Publish, schedule and take down. Publish a draft or a live post's waiting changes, unpublish, schedule a post for a time (with its time zone, on Creator and Growth) or unschedule it, and make the same change across many posts at once, including publishing imported drafts with their original dates. For a live post, the owner and admins can also have it put the post on the day it first went out (a past date).

• Who can read a post. Make a post for everyone, for members, or for members on a tier and up. The change applies at once, even on a live post, so it should check with you before making a members-only post public. Limiting a post to a tier is for the owner and admins, and needs the Growth plan. So does hiding a tier post from members below the tier.

• Who can read the whole blog. Make the whole blog for everyone, for members, or for members on a tier and up. This moves every post below that up to it, and a post cannot then be opened to more people than the blog allows. It is for the owner and admins, and limiting the blog to a tier needs the Growth plan. See Posts only members can read.

• Edit and recover. Throw away a live post's unpublished changes, read a post's history and put an earlier version back, and save a post as a template.

• Check. Score a post against the same checklist as the editor's gauge, and read the blog's numbers, including what posts sold, as totals and never who bought (owner and admins, on Creator and Growth).

• Organise. Add and reorder categories, put posts in them, add guest authors and teammate profiles, and say who a post is by.

• Set the blog up. Turn it on or off, set its kind, name, headline and intro, its subscribe band and the band's words, its own address word, its home layout (Grid, List or Magazine), whether readers see post dates, whether the cover and galleries run wider, whether it is your homepage, and whether members get a tab for it in the member menu. Make a subscribe form. (Owner and admins.)

• Email a post. Make a draft email from a live post, for you to address and send in the console.

• Imports. Read another blog by its address and say what bringing it over would add, and read how a past import went.

• Work with your team (Growth). Submit a post for review and, for the owner and admins, approve it or send it back with a note. Assign a post to a teammate with a due date, and the teammate is told as they would be from the console. Read a post's team comments, start a thread or reply, and resolve or reopen one. A mention in a comment emails that teammate. It can edit a comment you wrote, which then reads Edited. It can see who is editing a post, and changes to a post a teammate is editing are refused unless you tell it to take over. With approval switched on, an editor's assistant submits a post for review instead of publishing it. The owner and admins can also switch Editors' posts need approval on or off. Deleting a comment stays in the console.

• Delete a post that was never published.

What stays in the console

• Starting and undoing an import.

• Setting up an email for when a scheduled post goes live to members or contacts.

• Turning on the emailing of new posts to subscribers, or pointing the subscribe band at a different list while new posts are emailed, because that chooses who a broadcast goes to.

• Deleting anything that has ever been live. It can take it back to a draft.

For everything an assistant can do across your community, and the permission screen you approve, see What an assistant can do and Assistant permissions and safety.