You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a form field is prefixed with private- (such as private-submitted_email), the data associated with the field won't be sent from the API to the client. This is useful for keeping sensitive user information safe.
But it also means that logged-in editors cannot edit private form fields in the application's editor. Do we want to give editors the ability to edit private data? If so, I think it will require changes on the API side.
@futuresoup -- do you think there's a strong use case for this?
The text was updated successfully, but these errors were encountered:
Hmm now that I think about this some more I realize we'd have to grant private data access to all admin groups, or we'd have to implement a new kind of private data access permission which we can selectively apply to datasets groups. That might be more trouble than it's worth.
Currently, when a form field is prefixed with
private-
(such asprivate-submitted_email
), the data associated with the field won't be sent from the API to the client. This is useful for keeping sensitive user information safe.But it also means that logged-in editors cannot edit private form fields in the application's editor. Do we want to give editors the ability to edit private data? If so, I think it will require changes on the API side.
@futuresoup -- do you think there's a strong use case for this?
The text was updated successfully, but these errors were encountered: