|
| 1 | +============================ |
| 2 | +Visibility and collaboration |
| 3 | +============================ |
| 4 | + |
| 5 | +Odoo allows you to set custom visibility settings for each project, enabling you to make your |
| 6 | +project available to everyone in your organization or restrict access to certain internal or |
| 7 | +external users. |
| 8 | + |
| 9 | +.. _project/visibility_collaboration/visibility-settings: |
| 10 | + |
| 11 | +Visibility settings |
| 12 | +=================== |
| 13 | + |
| 14 | +Open the :guilabel:`Project` app, click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis-v)` |
| 15 | +icon on a project’s card, and click on :guilabel:`Settings` in the drop-down menu. Then click on the |
| 16 | +:guilabel:`Settings` tab and choose among the three :guilabel:`Visibility` options: |
| 17 | + |
| 18 | +- :guilabel:`Invited internal users (private)`: When following a project, internal users will have |
| 19 | + access to all of its tasks without distinction. Otherwise, they will only have access to the |
| 20 | + specific tasks they are following. A user with the Project app administrator access rights level |
| 21 | + can still access the project and its tasks, even if they are not listed as followers. |
| 22 | +- :guilabel:`All internal users`: All internal users can access the project and all of its tasks |
| 23 | + without distinction. |
| 24 | +- :guilabel:`Invited portal users and all internal users (public)`: All internal users can access |
| 25 | + the project and all of its tasks without distinction. When following a project, portal users only |
| 26 | + have access to the specific tasks they are following. This option is selected by default. |
| 27 | + |
| 28 | +.. _project/visibility_collaboration/external-users: |
| 29 | + |
| 30 | +Inviting external users |
| 31 | +======================= |
| 32 | + |
| 33 | +When selecting :guilabel:`Invited portal users and all internal users (public)`, a |
| 34 | +:guilabel:`Share Project` button appears on top of the project’s settings page. Click on it to open |
| 35 | +a pop-up window that offers two options to give external users access to the project: |
| 36 | + |
| 37 | +#. Copy and share the :guilabel:`Public Link` displayed on top of the pop-up window. Anyone with |
| 38 | + this link can access the project in read mode. |
| 39 | +#. Or select a :guilabel:`Collaborator`, choose the :guilabel:`Access Mode`, and check the box to |
| 40 | + send an invitation to their email address. |
| 41 | + |
| 42 | + There are three types of :guilabel:`Access Mode` for your collaborators: |
| 43 | + |
| 44 | + - :guilabel:`Read`: collaborators can view tasks but cannot edit them. |
| 45 | + - :guilabel:`Edit with limited access`: Collaborators can view and edit tasks they follow in the |
| 46 | + Kanban view. |
| 47 | + - :guilabel:`Edit`: Collaborators can view and edit all tasks in the Kanban view and choose which |
| 48 | + tasks they want to follow. |
| 49 | + |
| 50 | +To revoke an invited collaborator's access, click the :icon:`fa-trash-o` :guilabel:`(fa-trash-o)` |
| 51 | +icon next to their name, and click :guilabel:`Save`: to confirm. |
| 52 | + |
| 53 | +.. note:: |
| 54 | + In any case, an internal user with no project access rights can still access a task, provided |
| 55 | + that they are given the corresponding URL (and that they are part of the followers if the project |
| 56 | + is private). |
0 commit comments