Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

removing fields that cannot be sync'd due to access control settings from the sync options #140

Open
asirota opened this issue Apr 27, 2023 · 1 comment · Fixed by #169
Assignees
Milestone

Comments

@asirota
Copy link
Member

asirota commented Apr 27, 2023

Fields with No Access - internal use only (member) and Admin Access Only (contact) are only accessible and updated via a successful login for administrative users.

For regular non-admin users, these fields are not accessible via the API and as a result cannot be sync'd

Let's just eliminate from syncing in the Sync Options tab any field that is set to this way because it won't work and there's no reason to show it as a result.

The AdminOnly key in /accounts/:accountId/contactfields API call available via admin specifies these settings. If AdminOnly is set to true, we should not allow syncing of this field because these fields are not accessible to through the API for non-admin users.
We can list these fields below the checkboxes under the button so people know they are admin only, and can switch this value if they want the data sync'd

@asirota asirota added this to the 1.0.2 milestone Apr 27, 2023
@asirota
Copy link
Member Author

asirota commented Apr 27, 2023

We can also state to allow sync'ing of these fields please change the Member access option so that these fields are not set for administrative access only or "View only" for membership fields.

@asirota asirota modified the milestones: 1.0.2, 1.0.3 Sep 6, 2024
@asirota asirota assigned nataliebrotherton and unassigned mDisna Sep 27, 2024
@nataliebrotherton nataliebrotherton linked a pull request Oct 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants