Sharing a Project

Sharing a project with your team members and external stakeholders in Murf Studio is a breeze. You have the option to share a project from your home page or directly within the project itself.

In this article we will cover the following: 

There are 2 project sharing options available:

  1. Share Project: Sharing your project with team members and external stakeholders is made easy with the Share Project feature. This allows others to view the progress, provide feedback, and collaborate seamlessly directly within the Project.
  2. Share Preview: With the Share Preview feature, you can effortlessly create a one-of-a-kind link that enables you to share your project's particular builds in either video or audio format. You have the ability to update the link manually if there are any changes made to the project.

Share Project

By default, all new projects inherit their access permissions from the folder they are stored in. If the project is located outside of any folders, it is treated as if it were in a public folder.


Murf - Voice Settings

  • In the event that a user who is logged in attempts to access a project without proper permissions, a prompt will appear requesting access.
  • If the user is not logged in, they will also be prompted to enter their email address when requesting access.
  • For Enterprise customers, if a project is stored in a private folder and shared with a user who does not have access to the private folder, the project will appear in the "Shared with me" folder. This folder can be accessed through the left folder panel and allows users to view and collaborate on the project.

Preview Project

When opting for project preview,  a unique link with or without a password will be generated for each update made by the user. Both logged-in and non-logged-in users can view the project's output.

Murf - Voice Settings (1)


Invite and Access Management

Murf - Voice Settings (4)The invite tab allows users to invite team members with specific permissions to collaborate on a project. This feature allows you to invite both existing and new editors or viewers, while also restricting access as necessary.

Plan based Access Management

Free, Basic and Pro Plan

When a new editor or viewer who is not currently a member of the workspace is invited from a project, they will be added as a full editor/viewer.

The user will receive a confirmation message informing them of their new access level.

Enterprise Plan

When inviting an editor or viewer who is not currently part of the workspace from a project, they will be added as either a viewer-restricted or editor-restricted in the workspace. This ensures that they only have access to the specific items that have been shared with them.

Additionally, an editor or editor-restricted can invite a new user to the project as an editor-restricted, only if there are seats available in the workspace, without requiring payment. 

View States

Logged in user with View permissions (View-Only)

  • When in the View-only state, the user can observe the project and leave comments while also having access to the live project status.
  • The user will always view the newest rendered timeline, and any changes made by an editor will be immediately visible to the viewer.
  • The viewers will also be able to access the voice selector and explore the various voices.

Logged in user with Edit permissions (Edit-Only)

  • Users with editing permissions will be able to access the edit state of the project.
  • If the project is currently being edited by someone else, the user will be directed to the view-only state with the option to take control.

Logged in user with or without permissions through Share Preview link

  • Regardless of whether the user has a password or not, they will be able to view the project's output.

Request Access: Edit and View

Free, Basic and Pro Plan

  • If a viewer wants to edit a project, they can click on the "request to edit" button.
  • This will display a list of editors who have permission to edit the project.
  • The viewer can select multiple editors to send the request to.
  • It will then be up to the editors to decide whether or not to grant the viewer editing access.


  • If a viewer wants to edit a project, they can click on the "request to edit" button.
  • This action will prompt a list of admins who can upgrade them to an editor.
  • The viewer will have the option to select multiple admins to send the request to.
  • The admins can then decide to grant the user editing access.
  • If the user is already an editor, the list will also include the owner of the project and the admins to grant them edit access to the project.