Publishing from the app

How owners and admins publish their organization's staged changes from an iPhone, iPad or Mac an owner approved

AD-5For organization adminsAll sections ↓

Owners and admins publish changes to their organization's setup straight from the app, on any iPhone, iPad or Mac an owner has approved. Members never see any of this.

Approval is asked for by itself

Publishing needs a device an owner approved. You don't have to ask: the first time you stage a change in the Library on this iPhone (or iPad, or Mac), the app makes a publishing key for it and asks your organization's owners to approve it. The key stays on this device: it lives in the device's keychain, unlocked by Face ID, Touch ID, your passcode or your Mac's password, and is never synced or sent anywhere. If the key needs Face ID, it asks then.

Staged changes, the top of the Library and a streamline's What the assistant reads side then show a card: Waiting for Priya Nair to approve (or whoever your owners are), with the device's Fingerprint, four groups of letters and numbers. Your staged changes are kept on this device while you wait, and you publish them here once it is approved. Cancel Request withdraws it. If the request couldn't be sent (offline, for example), the card says why and offers Try Again.

On a device with no passcode the key is guarded by the device only. Set a passcode first if you can.

Members don't stage or publish: only owners and admins do. Members never see the Library, and a streamline's Theme card tells them who changes it.

An owner approves it

Nothing approves itself. Approving is the organization's business, so it happens where the organization's people are. When a device is waiting, an owner's approved device shows it in three places: Members marks the person's row 1 waiting; the person's page in Members has a Publishing section listing every device they publish from; and the top of the Library says 1 device is waiting for approval (the Library row in the sidebar carries a count).

Each request shows the person, their level (Owner or Admin), the device's name and its fingerprint. Before tapping Approve… and then Approve, compare the fingerprint on both screens: if they differ, tap Cancel, and Decline the request. Face ID, Touch ID or the passcode confirms the approval. The person's page then says Approved Oct 12 by Priya Nair.

An owner's device may publish everything; an admin's device may publish streamlines, briefs, templates and forms. No one can approve an admin's device until an owner has an approved device of their own, and the card says so. An owner's own new device asks for approval the same way, and another owner approves it.

The organization's very first owner device is approved with the organization's publisher key. For an organization Streamliner set up, ask Streamliner support (manolab) to approve this first device, and read them the fingerprint.

Once approved, the device reads the organization's whole setup, including each streamline's instructions, briefs and tool rules, so you can edit them in the Library. Read Setup Again (on Staged changes, and on your own page in Members) fetches the newest version.

Publish

Make your changes in the Library and stage them (The Library, LIB-1). Open Staged changes: the head of the page says Ready to publish. Tap Publish v…. The app first checks with your organization's account and shows Publish version …?: what the account said (Accepted · nothing written yet), the version, how many files are written and removed, and every change line by line. Tap Publish v… again, then confirm with Face ID, Touch ID, your passcode or your Mac's password.

Everyone whose roles include those streamlines gets the new version on their next check, within a few minutes. If someone else published while you were confirming, your staged changes are merged onto their version and the app asks you to review and publish again.

When someone else changed the same thing

When another owner or admin publishes while you have changes staged, the app merges theirs with yours. Changes to different settings merge on their own. If you both changed the same setting, the page shows a Conflict card with how yours differs from theirs, and publishing waits until you choose: Keep Mine (yours replaces theirs when you publish) or Take the Server's (your change to that file is dropped). With Files on this Mac turned on (MAC-4), the other version is also in the folder beside your file, with .server before its extension; deleting that copy keeps yours.

Revoke

On a person's page in Members, Revoke… ends a device's publishing for good: an owner can revoke anyone's device, and you can revoke your own. Revoking this device also removes its copy of the setup. A revoked device doesn't ask again by itself: its card offers Ask Again, which makes a new key that needs a new approval. Leaving the organization revokes this device's key too.

In the Vault

The Vault shows one line for the open organization, Publishing key on this iPhone: Approved by Priya Nair, Waiting for approval, Revoked or None. Nothing is managed there: Manage in Members opens your own page.

The organization's own systems still decide what the assistant can do, whatever is published.

The same manual ships inside the app. This section as Markdown