edc-permissions
Simple classes for setting group permissions required for Edc deployments.
To add the default groups and permissions run the management command:
python manage.py update_edc_permissions
Default Groups
The default groups are required for the normal operation of an EDC deployment. The default groups are:
ACCOUNT_MANAGER: members may add/change and delete user accounts
ADMINISTRATION: members may view the Administration page
AUDITOR: members may view all forms but have no add/change permissions.
CLINIC: members may add/edit/delete all CRFs, Requisitions, Actions and other required clinic trial data entry forms. They may also view the Requisition page of the Lab section;
EVERYONE: members may access the EDC;
LAB: members may perform all functions in the Lab section (Edit requisitions, receive, process, pack, manage manifests, etc);
PHARMACY:
PII: members may view all personally identifiable data and edit forms that manage such data (Screening, Consents, Patient registration);
PII_VIEW: members may view personally identifiable data but have no add/edit permissions for any of the forms that store such data.
Default membership for Clinical staff:
EVERYONE
ADMINISTRATION
CLINIC
PII
Default membership for Laboratory technicians:
EVERYONE
ADMINISTRATION
LAB
PII_VIEW
Default membership for Auditors:
EVERYONE
ADMINISTRATION
AUDITOR
PII_VIEW
** Permissions **
Permissions use Django’s permission framework, therefore, all permissions are linked to some model.
Permissions don’t always naturally link to a model. In such cases, a dummy model is created. For example, with Navigation bars from edc_navbar. Permissions to follow an item on a navigation bar are associated with model edc_navbar.Navbar. A similar approach is used for listboard permissions using edc_dashboard.Dashboard.
Metadata
Release files for edc-permissions 0.1.48
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| edc_permissions-0.1.48-py3-none-any.whl | Python 3 | none | any | Details for edc_permissions-0.1.48-py3-none-any.whl |
Release files / edc_permissions-0.1.48-py3-none-any.whl
| Download URL | edc_permissions-0.1.48-py3-none-any.whl |
|---|---|
| Size | 33.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a2dc7181399f4b056d758ca35bb1d17959fa0b45fbb33ba10311bf08740d9a8
|
|
BLAKE2b-256 checksum How to use checksums |
43fb773d9c6266e9a9add60f8b4a8e9f81556a775ad53e95467dab48c48385fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4
|
Security for edc-permissions 0.1.48
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.