mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
92a41aa849
* docs(P13c): reconcile Configure content drift — audit log/telemetry cleanup, mobile ephemeral mode, watermarking, plugin/integration defaults, CJK fix Ports content drift from the legacy mattermost/docs Sphinx repo into the Administration Guide > Configure MDX pages (phase P13, sub-phase P13c): - environment-configuration-settings: remove unused ExperimentalAuditSettings file-rotation settings (now handled via AdvancedLoggingJSON), update EnableDiagnostics description to reflect Rudder/telemetry removal (Sentry only), and add the Mobile ephemeral mode settings. - experimental-configuration-settings: remove the same unused audit logging settings, and add the experimental Enable Mobile Watermark setting. - site-configuration-settings: update Report a Problem default behavior and fix the ReportAProblemMail env var name, add Channel category sorting, and add the Classification Markings section. - integrations-configuration-settings: fix OutgoingIntegrationRequestsTimeout key name and default value. - plugins-configuration-settings: fix RequirePluginSignature default (false). - reporting-configuration-settings: rename Site statistics to System statistics, preserving the legacy anchor. - enabling-chinese-japanese-korean-search: fix missing semicolon in the zhparser SQL example. - system-attributes: rename "Custom attributes for user profiles" to "User attributes" to match the v11.7 product rename. authentication-configuration-settings had no net drift to apply: the source commit reviewed (LDAP/SAML ID case-sensitivity notes) was later reverted upstream, and Azure Blob Storage documentation (hinted in the task) was also added then fully reverted upstream, so no Azure content exists in either the source or target repo. * docs(P13c): fix config.json key for Enable Mobile Watermark setting ExperimentalSettings.EnableMobileWatermark does not exist in config.go; the actual field is ExperimentalSettings.EnableWatermark. --------- Co-authored-by: Hanzo Dev <[email protected]>
15 lines
1.8 KiB
Plaintext
15 lines
1.8 KiB
Plaintext
---
|
|
title: "System Attributes"
|
|
---
|
|
<PlanAvailability slug="ent-plus" />
|
|
|
|
System attributes configuration settings provide system admins with centralized control over key user account properties.
|
|
|
|
Review and manage the following system attributes configuration options in the System Console by selecting the **Product** <img src="/img/ui/products_E82F.svg" alt="Navigate between Channels, collaborative playbooks, and boards using the product menu icon." className="theme-icon" /> menu, selecting **System Console**, and then selecting **System Attributes**.
|
|
|
|
You can define, manage, and enforce specific attributes, including:
|
|
|
|
- **User attributes**: Display details such as job titles, departments, or other metadata, on user profiles that align with your organizational structures and workflows. Learn more about [managing user attributes](/administration-guide/manage/admin/user-attributes). API responses for user attributes return default visibility and sort order when those values are missing.
|
|
- **Granular access controls based on user attributes**: Ensure users have access to only the resources and functionality relevant to their roles, bolstering security and compliance across the organization. Learn more about [managing access based on user attributes](/administration-guide/manage/admin/attribute-based-access-control).
|
|
- **Control user-managed attributes in attribute-based access control (ABAC)**: From Mattermost v10.11 (Enterprise Edition Advanced), user-managed attributes are excluded from ABAC rules by default to prevent unauthorized access. System admins can enable them with a configuration setting. Learn more about enabling user-managed attributes in ABAC rules in the [User Attributes documentation](/administration-guide/manage/admin/user-attributes#before-you-begin).
|