Problem/Motivation

There are permissions that allow users to view/update their mapped contact. This requires roles, and does not allow for finer control.

Steps to reproduce

Proposed resolution

Add boolean fields to the crm_user_contact_mapping for label, view, update, delete. Users with 'administer crm' permission can set the values. The User Contact Mapping form should have additional fields to allow site builders to set default values to: label, view, update, delete.

When the crm_user_contact_mapping is created or updated, rebuild grants for the mapped contact.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork crm-3565327

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

bluegeek9 created an issue. See original summary.

bluegeek9’s picture

Status: Active » Postponed
bluegeek9’s picture

Title: Contact access: User Maping » Contact access: User Mapping
bluegeek9’s picture

Status: Postponed » Active
jdleonard’s picture

Issue summary: View changes

Fixed typos in IS.

This seems sensible. I'd suggest that there be a setting for the default behavior and that the proposed fields provide Mapping-specific overrides of that behavior. That way the default can be changed and/or specific overrides can be changed.

bluegeek9’s picture

Status: Active » Needs review
bluegeek9’s picture

Status: Needs review » Fixed
//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:
  • Triage issues and adding more context to existing issues.
  • Flagging CRM as a favorite on the project page to help others discover it and show your support.
  • Review the Developer Docs for accuracy and clarity.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.