Skip to main content

User profiles

Project description

Beta License: AGPL-3 OCA/server-backend Translate me on Weblate Try me on Runboat

Extending the base_user_role module, this one adds the notion of profiles. Effectively profiles act as an additional filter to how the roles are used.

This allows users to switch their permission groups dynamically. This can be useful for example to:

  • finer grain control on menu and model permissions (with record rules this becomes very flexible)

  • break down complicated menus into simpler ones

  • easily restrict users accidentally editing or creating records in O2M fields and in general misusing the interface, instead of excessively explaining things to them

When you define a role, you have the possibility to link it to a profile. Roles are applied to users in the following way:

  • Apply user’s roles without profiles in any case

  • Apply user’s roles that are linked to the currently selected profile

In addition you can:

  • Add a ‘no profile’ profile to the user’s choice of profile, to allow him to select a specific profile which enables only the roles without a profile.

  • Restrict the user to change its profile, which can be useful in a security emergency.

Table of contents

Configuration

To configure this module, you need to go to Configuration / Users / Profiles, and create a new profile.

Then go to Configuration / Users / Roles and set some roles with a profile.

Then go to Configuration / Users / Users and add some roles if not already done. The allowed profiles will computes automatically.

In addition you can:

  • Check the “Include Default Profile” box to have the default profile as an allowed profile.

  • Change the current profile if needed.

  • Check the “Restrict Profile Switching” to restrict the user to change it’s profile, in that case you can still change it from the user’s settings form.

Usage

Once you have set up at least one profile for a user, use the widget in the top bar to switch user profiles. Note that it is possible to use no profile; in this case, the user will only get the roles that always apply (i.e the ones with no profile_id).

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Akretion

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/server-backend project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


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

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_base_user_role_profile-18.0.1.0.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_base_user_role_profile-18.0.1.0.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 e0bcb46566d5c8844de17fcfccc8978a7cd3f221d099dabf81c2e150477c7be8
MD5 1af813b69ff3d138be8ee1a803cc790d
BLAKE2b-256 9ff8b14d799b4f42bba499c0ca5b796be0a6e93bb33d8da969729e5dcbeecb96

See more details on using hashes here.

Supported by

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