> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/collaborating/sharing-a-project.md). # Sharing a project Collaborating is what makes Overleaf special. Follow these steps to get started. ## Steps {% stepper %} {% step %} ### Click Share Click on the **Share** button (top right).

A screenshot of an arrow pointing to the Share button in the top right corner of the toolbar.

{% endstep %} {% step %} ### Choose a sharing method and permission level There are two ways to share a project with your collaborators. You can always update or revoke these permissions through the **Share** menu. Jump ahead to understand more about [permissions levels](#understanding-permission-levels).

The Share menu showing the audience toggle open. The two options are 1. Only invited people and 2. Anyone with the link (selected).

#### By Email 1. Invite specific collaborators by typing in their email(s), choosing their permission level, and clicking **Invite**. 2. Your collaborator(s) will receive an email inviting them to join the project. 3. Once their account is authenticated, they will be able to accept the invite and collaborate on the project. 4. At that point, the **Manage access** menu will update to remove the *Pending invite* tag. {% hint style="info" %} Getting an error? You might be running into group subscription settings. {% endhint %} #### By Link Links are a more flexible way of sharing your project. You can embed a project link in a document or share with a wider audience that might be interested. {% hint style="warning" %} Collaborators that join through a link *do not* show in the **Manage access** menu. To update their permissions, update the link permission level. Anyone who joined through the link will have their permissions updated. {% endhint %} To generate a link: 1. Choose your audience. Select **Anyone with the link** (instead of the default **Only invited people**). 2. Set the permission level for the link. The [permission level](#understanding-permission-levels) is set to **Viewer** by default. The other options are **Reviewer** and **Editor**.

A list of three options for the share link permissions. They are Editor, Reviewer, and Viewer. The Viewer option is selected, highlighted in green with a checkmark.

3. Click

(bottom left). {% endstep %} {% step %} ### Start collaborating * Highlight troublesome code and [comment](https://docs.overleaf.com/collaborating/commenting#using-comments) on it directly. * Allow collaborators to [suggest changes or respond to comments](https://docs.overleaf.com/collaborating/reviewing-and-reviewers#changing-a-collaborators-mode#reviewer-permissions). * Inviting someone to transfer ownership? Learn more [here](https://docs.overleaf.com/collaborating/transferring-project-ownership). {% endstep %} {% endstepper %} ## Understanding permission levels Ensure you grant the right access.

			Cover image
Lowest Access (Default)	Use Case	Read-only Template, Large Audience	Viewer only.png
Medium Access	Use Case	Troubleshooting Advice, Chapter/ Section Feedback	Reviwer only.png
Highest Access	Use Case	Co-authoring, Group Projects	Editor only.png

Want to know about specific functionality access?

Permission Level	View Source Code	Download Source & PDF	Copy the Project	View Comments	Write Comments	Suggest Edits	Edit Source Code & Add Files	Accept/ Reject Changes	Restore Versions
Viewer	true	true	true	true	false	false	false	false	false
Reviewer	true	true	true	true	true	true	false	false	false
Editor	true	true	true	true	true	true	true	true	true

## Manage access Click **Manage access** to update individual permissions, and resend or revoke pending email invites.

## Frequently Asked Questions #### Are my Overleaf projects private? Yes, every project you create is automatically private. Other Overleaf users cannot see your projects in Overleaf unless you deliberately share them with others via the **Share** menu. When link sharing is enabled, Overleaf creates a unique token used only for the link to that project. It is almost impossible to guess the token, and hence the link to your project is known only to you. For more information, please see the Privacy Policy tab on our [Terms of Service](https://www.overleaf.com/legal) page. {% hint style="warning" %} If you turn link sharing on, please note that if you publish the link to your project on a website or somewhere public, *anybody* can use the link to *view and download* your project. The website where your link is posted might even be included in search engine results. {% endhint %} #### More FAQs

How many collaborators are allowed?

Adding more than one collaborator per project (editor or reviewer) is a [premium feature](/getting-started/free-and-premium-plans/premium-features.md). Overleaf premium features are available to users whose organization or university has an [Overleaf Commons](https://www.overleaf.com/for/universities) subscription, members of [group subscriptions](https://www.overleaf.com/user/subscription/plans#group), and owners of [individual subscriptions](https://www.overleaf.com/user/subscription/plans). The number of collaborators you are allowed to invite will depend on the plan you are part of. Visit our [plans page](https://www.overleaf.com/user/subscription/plans) to view the different plans available.

Not seeing the invite?

Please try the following: * Make sure the email address you are using is correct. * Try resending the email by clicking **Resend** in the **Share Menu**. * Check the spam folder of the email address as sometimes emails can end up there by mistake. {% hint style="info" %} If that didn't solve the issue please reach out directly to [support@overleaf.com](mailto:). {% endhint %}

Can link sharing be turned off again?

Yes. Project owners can remove at any time through the Share menu by switching the link setting back to **Only invited people**.

The link setting toggle set to "Only invited people" instead of "Anyone with the link."

If the collaborator joined through... * **a share link** their permissions are removed. * **an email invite** their permissions are retained (use the [**Manage access**](#manage-access) menu to update invidividual permissions)

What about legacy sharing links?

They still work. If your project has legacy sharing links you can maintain them as is, or swap to a single, stable sharing link by choosing a different option on the list. This will remove the original links and consolidate them into a single new one (after you confirm). {% hint style="danger" %} This is a permanent change. You cannot go back to a dual **view**/ **edit** link option. {% endhint %}

A pop-up warning that says: "This change will permanently remove your original sharing links. You can still share a new link to the project when you choose a relevant sharing option. There are two options: 1. to Cancel and 2. Remove original links (red)

Do share links expire?

No. Links do not expire, but the owner can deactivate them by switching the link setting back to **Only invited people**.

{% hint style="info" %} Not seeing your issue above? Please reach out directly to [support@overleaf.com](mailto:). {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.overleaf.com/collaborating/sharing-a-project.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.