Mini UX Spec: Auto-Add Members Feature
Purpose
Enable automatic addition of users to private channels when they satisfy ALL access requirements (system policies + custom channel rules).
Approach 1 — Auto-add as single toggle in system polcies
Core Principles
Auto-add evaluates the combined requirements of all system policies and custom channel rules
System admins have hierarchical precedence over channel admins
Users must match ALL requirements to be automatically added
Control Model
System admins can force auto-add through policies
Channel admins can enable auto-add if not forced by system
Auto-add is ON if system forces it OR channel admin enables it
Policy Creation/Editing
When creating or editing an access policy in the System Console, system admins will see an "Auto-add members based on access rules" while creating/editing the policy . This section presents two options:
Do not auto-add members (default): Channel admins retain control over whether to enable auto-add
Force auto-add members: Overrides channel admin preferences and automatically adds qualifying users to all channels where this policy is applied
Channel Admin Auto-Add Control
The auto-add control appears differently based on system policy settings:
Scenario A - System Enforced: If any system policy forces auto-add, the checkbox is checked and read-only. An information message explains which policy is enforcing auto-add and that it cannot be modified at the channel level.
Scenario B - Channel Control: If no system policy forces auto-add, channel admins see an editable checkbox they can toggle. When saving, they're shown a preview of who would be immediately added.
Auto-Add Evaluation Logic
Determining Auto-Add Status
The system determines if auto-add is enabled for a channel using the following logic:
First, check all system policies applied to the channel
If ANY system policy has "Force auto-add" enabled, auto-add is ON for the channel
If no system policy forces auto-add, defer to the channel admin's setting
The result is a binary state: auto-add is either ON or OFF for the channel
Permission Matrix
Scenario | System Policy setting | Can Channel Admin modify? | Channel Admin auto-add setting | Final auto-add state |
|---|---|---|---|---|
No system policy | N/A | Yes | OFF (default) | OFF |
No system policy | N/A | Yes | ON | ON |
System policy without auto-add | No auto-add | Yes | OFF (default) | OFF |
System policy without auto-add | No auto-add | Yes | ON | ON |
System policy with forced auto-add | Force auto-add | No | N/A (read-only UI) | ON |
Multiple policies (at least one forces) | Mixed | No | N/A (read-only UI) | ON |
Multiple policies (none force) | No auto-add | Yes | OFF (default) | OFF |
Multiple policies (none force) | No auto-add | Yes | ON | ON |
Conflicting System Policies
When multiple system policies apply to a channel with different auto-add settings:
If ANY policy forces auto-add, it takes precedence
The UI clearly shows which policy is enforcing auto-add
The combined requirements from ALL policies still apply for user eligibility
Approach 2 — Auto-add as per channel configuration
If we were to treat AUTO-ADD as a channel level setting and allow it to be configured per channel in system access policies as well:
Core Principles
Auto-add is a channel-level setting that can be modified from multiple interfaces
Both system admins and channel admins have equal control over the auto-add toggle
Users must match ALL requirements to be automatically added
Control Model
Channel-Centric Control:
Auto-add is a property of the channel, not the policy
System admins can toggle auto-add for specific channels when creating/editing policies
Channel admins can toggle auto-add in channel settings
The setting is synchronized - changing it in one place updates it everywhere
Benefits of This Approach
Greater channel autonomy: Channel admins maintain control over their channels
Flexibility: System admins can suggest/implement auto-add without forcing it
Clarity: One setting per channel, regardless of how many policies apply
Simpler permission model: No hierarchy or override logic needed
Potential Challenges
Synchronization complexity: Changes in one policy view affect all other policy views
Attribution confusion: Unclear who last changed the setting or why
Compliance concerns: System admins cannot enforce auto-add for regulatory requirements
Discovery issue: Channel admins might not know system admin enabled auto-add via a policy
Multi-Policy Synchronization
When a channel appears in multiple policies:
The auto-add toggle shows the same state in all policies
Changing it in Policy A immediately updates the display in Policy B
A note appears: "Auto-add is a channel setting. Changes here affect all policies."
Auto-Add Control Section:
Single checkbox: "Auto-add members who match all access requirements"
Last modified information: "Last changed by [System Admin] 2 hours ago"