Skip to main content

Authentication for clinicedc/edc projects.

Project description

pypi actions codecov downloads

edc-auth

Authentication and permissions for the Edc

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.

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.

Importing users

You create user accounts by importing a specially formatted CSV file. Once an account is created a “Welcome” email may be sent.

Import users from a CSV file with columns:

    username
    first_name
    last_name
job_title
email
alternate_email
mobile
sites: a comma-separated list of sites
groups: a comma-separated list of groups

Then import the users from your application commandline

python manage.py import_users --csvfile=/Users/erikvw/meta_users.csv --notify-to-test-email=ew2789@gmail --resource-name=meta.clinicedc.org --resend-as-new

Legacy notes

Important: If you are upgrading from edc_base.auth:

The userprofile table is now in edc_auth. edc_auth has one migration for this table. Copy the same table from edc_base and fake the edc_auth migration.

CREATE TABLE edc_auth_userprofile LIKE edc_base_userprofile;

INSERT edc_auth_userprofile SELECT * FROM edc_base_userprofile;
python manage.py migrate edc_auth --fake

You can now run the edc_base migration safely.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

edc_auth-0.3.14-py2.py3-none-any.whl (83.1 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file edc_auth-0.3.14-py2.py3-none-any.whl.

File metadata

  • Download URL: edc_auth-0.3.14-py2.py3-none-any.whl
  • Upload date:
  • Size: 83.1 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5

File hashes

Hashes for edc_auth-0.3.14-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 99f18a5af954e97482f0950ffd91a0ae5fb569589e7e38a9a5e0a64844b7267c
MD5 4bcc57141174c0de3a093b3483a61bef
BLAKE2b-256 cb355529f0ed0948afb8dfa4dd320b4ff35ba0f73a7bc12e0a7881eb879dec10

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page