Search 1.9 billion lines of Odoo code on GitHub
project_security_group
| Author: | Daniel Reis, Odoo Community Association (OCA) |
|---|---|
| License: | AGPL-3 |
| Branch: | 9.0-port-base-user |
| Repository: | dreispt/project |
| Dependencies: | project, and project_stage_state |
| Languages: | Markdown (43, 19.5%), PO File (46, 20.8%), Python (26, 11.8%), XML (65, 29.4%), and reStructuredText (41, 18.6%) |
| Other repositories: | JesusZapata/project, and incaser/project |
<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg">
</a>
<a name="project-management-security-groups"></a>
<h2>Project Management Security Groups</h2>
<p>Project User permissions are reduced, so that they cannot edit Tasks
(or Issues) not in the "New" and "Cancelled" states.
This makes it suitable for end users, that can create new requests
(and edit or cancel while they are still drafts) but can't
modify them once their resolutuion has been started by the project team.</p>
<p>Two additional groups are added, based on the project User group:</p>
<ul class="simple">
<li>"User: Can Edit Tasks/Issues": is for the project team,
and can edit Tasks (or Issues) in any state.</li>
<li>"User: Manage Own Projects": has additional permissions to create Projects
and related configurations.</li>
</ul>
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/140/9.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
<a name="configuration"></a>
<h3>Configuration</h3>
<p>The existing Project Stages need to be mapped into proper States.
That's how we know what are "New" and "Cancelled" items.
Check the "Project Stage State" module <cite>documentation <https://github.com/OCA/project/tree/9.0/project_stage_state></cite>
for for information.</p>
<p>After installing this module, review the Users with access to the Project app,
since at least some of them will need to have their access group changed to one of the new ones.</p>
<a name="usage"></a>
<h3>Usage</h3>
<a name="known-issues-roadmap"></a>
<h3>Known issues / Roadmap</h3>
<a name="credits"></a>
<h3 class="with-subtitle">Credits</h3>
<h3 class="section-subtitle" id="contributors"><span class="section-subtitle">Contributors</span></h3>
<ul class="simple">
<li>Daniel Reis <dreis.pt at hotmail.com></li>
</ul>
<a name="maintainer"></a>
<h3>Maintainer</h3>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/project/issues">GitHub Issues</a>. In case of trouble, please
check there if your issue has already been reported. If you spotted it first,
help us smash it by providing detailed and welcomed feedback.</p>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>