How to set editing permissions for document collaboration

Key points of this article

Before setting permissions, distinguish who only needs to see and who needs to change. Do not give others more permissions than they need for their actual work.
Editing permissions are only given to those who really want to modify the content, and those who only need to review can use viewing permissions.
Send the file as an email attachment. If the other party changes the copy, the modification will not return to the original file. Collaboration should use a shared link instead.
After sending the link, open it with another account or an incognito window to confirm that the permissions seen by the other party are consistent with your expectations.
After the project ends or personnel changes, access rights that are no longer needed are promptly recovered to prevent old links from being valid for a long time.

When multiple people write a plan, review a contract, or revise a report, many people will encounter the same problem: Who should the document be edited and who should only read it? If the permissions are given too wide, the content will be easily modified by mistake; if the permissions are given too narrowly, the other party will not be able to open or modify it, and will have to send attachments back and forth. The core of how to set editing permissions for collaborative documents is to first think clearly about each person's role, and then implement the corresponding access methods into specific sharing actions.

This article is for individuals and teams who need to share Word documents and talks about how to set "who can view and who can edit". This article will use the general concept of permissions and use OmniDoc's shared link as an example to illustrate the operation. After reading, you can determine what permissions each person should get, know how to send it out, and know what to check after sending it out. How to turn on or off the collaboration function is beyond the scope of this article.

How to set editing permissions for collaborative documents? One sentence conclusion

Let me answer in one sentence first: Determine the permissions based on each person's actual work content. Only give editing permissions to those who want to change the content, and view permissions for the rest. Send them through a shared link instead of directly sending attachments.

Your situation.	Recommended practices	Reason
The other party only needs to read the content or make comments.	Give viewing permission, or share via link read-only	Avoid mismodification of the text and keep the original document stable
The other party needs to modify the text directly.	Give editing permission and explain the scope of modification	The changes fall directly on the same file without merging back and forth.
The other party only needs to sign and confirm and do not change the content.	Send a PDF using a signing request	Signing and content editing are two different things, and editors should not be given permission.
The document contains sensitive contents such as contract amount and personal information.	Only send it to the designated person, do not send a public link	Once the link is forwarded, there is no control over who can see it
Project has ended or member has left	Withdraw the permission and create a new copy to share if necessary	The long-term existence of old permissions will bring risks of mistaken modification and leakage.

Before you start: Confirm these points first

Before setting it up, it is recommended to take a few minutes to confirm the following things. They determine which permissions you want to use and whether there will be any problems after setting them up.

Confirm everyone's role. Divide participants into three categories: "want to change content", "just don't want to change" and "just need to sign". If the roles are not clearly defined, editing will be opened directly. It is easy for multiple people to change the same paragraph at the same time and overwrite each other.
Confirm file format. This article uses Word (.docx) as an example. If you want to edit directly on the web page, you can use the UniDoc web editor to open the .docx file, which supports editing compatible with Word; if you only need the other party to view it, PDF can also be used, but PDF is not suitable as a collaborative manuscript that requires continuous modification.
Confirm sharing method. If you send the file as an email attachment or chat software file, the other party will get a copy, and subsequent modifications will not be synchronized. When multiple people need to work on the same document at the same time, a shared link should be used to let everyone point to the same content.
Confirm the other party’s account and device. If the other party does not have a corresponding account, or the device used does not support online editing, it cannot be opened normally even if the permissions are set correctly. Asking questions in advance can avoid detours.
Confirm the modified rules. For example, who is responsible for the final draft, which chapters can be modified directly, and which can only be left with comments. Permissions can only control "whether it can be changed". Modifying the rules must be agreed upon by the team themselves.

# steps to set sharing permissions on UniDoc web pages

The following steps take the UniDoc web page editor as an example and apply to Word documents that need to collaborate online.

Open app.unidoc.top in a browser and log in to open the document that you need to collaborate with. If the document has not been uploaded, import your .docx file first.

two. Find the entry of sharing-related functions in the document and go to the sharing settings page. The location of the interface may vary slightly from version to version, depending on what you are currently seeing.

Check the sharing status of the current document. If a link has been generated before, check to see if the link is still there and who is using it, and then decide whether to use it or not.
Determine the access method for those who need to modify the content. If the sharing interface provides two options: view and edit, it corresponds to the choice; if only one access method is provided, follow this one, and do not assume that there are more detailed gears.
Generate a sharing link. After the link is generated, copy it first and do not paste it directly into a public group chat or web page.
Send the link only to the corresponding person, and write clearly in the message: what the other party is allowed to do, whether it is only to see or can be modified, and which chapters to modify it.
If someone needs to sign and confirm rather than change the content, please use the signature request function to send the PDF to the other party for online signature, and do not open up editing rights for signature.
After sending, make a note of who the link was sent and when it was sent, so that it can be checked and withdrawn later.

# check item by item after completion

After the permission setting is complete, do not directly assume that it is foolproof. It is recommended to check item by item with the table below, especially when collaborating with new colleagues for the first time.

Check item	What do you think?	What if there's a problem?
Check whether the permission is in effect	Open the link with another account or trackless window to make sure you can see the content	If you can't see it, check whether the link is copied completely, or whether the other party's account has access conditions.
Whether the editing permission is only given to the person who should be given it.	Check the list of recipients of the link and make sure it is not forwarded to an irrelevant group chat	If you find the spread, take back the link immediately, regenerate it and send it to the designated person only.
Whether the editing scope is in accordance with the convention	Check against the modification rules to see if the changes fall in the allowed section	Out-of-scope changes are withdrawn in the revision record and rules are explained within the team
Whether the viewer has mistakenly acquired the editing ability	Ask the viewer to try to modify a piece of text to see if it is restricted	If you can modify it, check the type of link it uses and re-share it in read-only mode.
Whether sensitive content can be accessed externally	Confirm whether the contract amount and personal information are included in the document.	Delete or replace sensitive parts, or revoke public links

If the content is found to be incorrect, such as numbers, dates or proper nouns, it should be modified according to the original data, and do not default that the other party has been verified just because it is a collaborative document. Content involving machine translation or text recognition should also be reviewed item by item against the original text.

# Summary

The key to how to set editing permissions for collaborative documents is to distinguish by role who only looks, who wants to change, and who only needs to sign, and then use the sharing link to send the corresponding access to the designated person. After setting up, open it with another account, confirm that the permissions are the same as expected, and withdraw in time after the end of the project. In this way, document collaboration can not only maintain the unity of content, but also will not cause miscorrection or leakage because of too wide permissions.

# frequently asked questions (FAQ)

1. Send the Word file directly to email, can the other party change it with me?

Cannot synchronize in real time. The email attachment is a copy, which needs to be sent back after the other party has modified it. If you merge it manually, it is easy to have a confused version. Multiple people are required to work on the same document at the same time, and sharing links should be used.

2. Only given the permission to view, the other party can still copy the content, what to do?

The view permission can only restrict the modification and cannot prevent the other party from copying or taking screenshots. If the content is sensitive, you should only send it to those who are necessary, and agree on confidentiality requirements within the team. Do not rely on permissions to keep secrets.

3. How to set up document collaboration to prevent others from mistakenly deleting content?

The direct way is to give editing permissions only to those who need to modify them, while others use view permissions. At the same time, you can make an agreement within the team: keep a copy of the important paragraph before you change it, or indicate the reason for the change in the change record.

4. The other party does not have an account, can you directly use the link to edit?

It depends on the way you share and the version of the feature you use. Confirm the access conditions in the sharing settings before operation, and test them with another device. If the other party can not open, follow the interface prompts to adjust, do not temporarily change the link to public.

5. After setting the permissions, do you still need to check regularly?

Need. The transfer of personnel, the end of the project, or the forwarding of the link to the outside world will invalidate the original permission settings. It is recommended that at the end of each project phase, go back to the sharing settings page to check which links are still in use and take them back in time if they are no longer needed.

Open OmniDoc to edit and export documents online