Project

General

Profile

Actions
Copy link

Feature proposal #3973

closed

Implement admin forced privacy settings

Added by krileon over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
krileon
Target version:
3.0.0
Start date:
15 April 2013
Due date:
% Done:

100%

Estimated time:

Description

Implement option to force a privacy value for a field, tab, or profile by backend configuration so it behaves as if the user selected the privacy but don't display the privacy selector to the user.

Actions
Copy link
 #1

Updated by krileon over 11 years ago

  • Target version set to 3.0.0
Actions
Copy link
 #2

Updated by krileon over 11 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

When enabling privacy it can now be set to "Moderators can control privacy", which allows CB Moderators to adjust privacy for the field and/or tab, but not anyone else. This can be used to force a privacy setting to a field that a user won't be able to change.

Actions
Copy link
 #3

Updated by krileon over 11 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF