Sharing and permissions

Account and server required

Sharing is available in server-backed workspaces. You need permission to manage the project or folder.

Invite someone to a project

1. Open the project’s Share dialog.
2. Enter the person’s email address.
3. Choose Editor or Viewer.
4. Add the member and check that the person appears in the access list.

An editor can modify the document within the permissions granted by the workspace. A viewer can read it but cannot edit the source. Ownership and access management are separate from simply being an editor.

Share a folder

Use the folder’s sharing action to grant access through its hierarchy. Projects can inherit access from a containing folder. If someone still has access after removal from a project’s direct member list, check folder membership too.

Only the project owner can move a document between folders, including moving it back to the dashboard root. The destination folder must belong to that owner. Editors can edit a shared document, but cannot change its inherited access by moving it. A folder can only be nested inside another folder belonging to the same owner.

In the sample manuscript shown here, Sam needs can edit access to revise the methods and leave comments. Léa has can view access for reading. Give a reviewer Editor access if they need to write comments in the current app. The person must have signed in to Tylor at least once before you can add them.

Work at the same time

Inviting an editor grants access; real-time collaboration is a separate project setting when supported by your instance.

Share only the rendered PDF

Use a public PDF link when readers only need the output. Anyone with that link can access it. For restricted source access, invite members instead.

If compilation fails, public-link readers see a short error asking them to contact the owner. Source excerpts and detailed compiler diagnostics remain available through the editor to authorized members. Revoking a link stops future downloads; it cannot remove copies someone already downloaded.

To give a collaborator an independently owned document, direct them to Make a personal copy.

If copying a public PDF link fails, Tylor shows an error instead of a success checkmark. Select the displayed URL and copy it manually, or retry Copy public link.

For older deployments using legacy Firestore storage, editors may edit document files and basic document metadata. Only the actual owner may change sharing or delete a project, and ownership cannot be reassigned by rewriting metadata.

On tylor.app, documents use the self-hosted Postgres backend and Firestore document access is disabled. Firebase remains the sign-in provider. The legacy restrictions above apply only to separately configured older installations.