Skip to main content
Letting an assistant work on your live academy should feel safe, so Fayne builds the checks in rather than relying on the assistant to be careful.

What goes live, and when

Your assistant is told which changes are live, so it describes them to you before making them.

Previews you confirm

Price changes, putting offers on sale, anything that emails people, and anything that changes someone’s access happen in two steps:
  1. Your assistant prepares the change. Nothing happens yet. You get a preview of exactly what will change: the old and new price, who will be emailed and what the email says, or who gains or loses access.
  2. After you say yes, it confirms. Fayne runs exactly what was previewed.
A preview lasts 10 minutes. If anything it depends on changed in the meantime, such as the price, the list or the people, the confirm is refused and your assistant prepares a fresh preview to show you.

Safe retries

Connections drop. If your assistant’s request times out, it can’t tell whether the change happened, so Fayne makes resending safe:
  • A confirm sent twice runs once. The second time returns the first result.
  • Other changes can carry a one-time key your assistant chooses. Sent again with the same key within a day, the change isn’t made twice; your assistant gets the result of the first one.
  • If a change failed partway, Fayne says so and tells your assistant to check the current state before trying again.

Working in the editor at the same time

You can keep a course open in the Fayne editor while your assistant works on it.
  • Its changes appear on their own, with a note that your assistant updated the lesson. New lessons and modules show up in the outline. While an assistant is working in your academy the editor checks every few seconds; otherwise about every 30 seconds, and at once whenever you come back to the tab.
  • Your unsaved typing is never overwritten. If your assistant changes a lesson you’re editing, the editor shows Your assistant changed this lesson with two choices:
    • Load latest shows your assistant’s version. Your unsaved edits to that lesson are discarded.
    • Keep mine saves your version over your assistant’s change.
  • Changes from another tab or a teammate are picked up the same way. If they hit a lesson you’re editing, the note reads Changed elsewhere, with the same two choices.
To avoid choosing between versions, let your assistant finish a lesson before you edit it, or tell it which lessons you’re working on.

Limits and checks

  • Plan limits. Creating courses and lessons counts against your plan, just like in the app. If you hit a limit, your assistant tells you in plain words; nothing is half-created.
  • Paused academies are read-only. Reads still work.
  • Rate limit. Up to 100 changes per connection every 60 seconds.
  • Checks on every image your assistant adds: type, size, and no scripts in SVGs. See Images and files.
  • Access you chose. Only the academies and areas you allowed. See Permissions.

Undoing a change

There’s no single undo button for assistant changes, but most changes are easy to reverse:
  • Lesson edits are drafts until published. Ask your assistant to change them back, or discard them in the editor.
  • Branding, links and course details: ask your assistant to set them back. It can read the current values first.
  • Prices and offers: prepare and confirm the old price again.
  • For anything else, contact support with the time and what changed.