Home
HCL Sametime® Administration Guide 12
Administering
This section provides information on administering on Sametime environments.
Managing policies
Sametime policies allows administrators to control user access to features.
Configuring policies
In previous versions of Sametime there was a graphical user interface available to configure policies. In Sametime 12.0 configuring policies are done in the policies.user.xml file, which is located on the Sametime server.
Managing policies on Docker
This section outlines the steps on how to manage policies in a Docker environment.

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
  - Managing Sametime clients
    This section provides information on managing Sametime clients.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
  - Testing Sametime chat and meeting clients
    This article assumes that you have successfully installed and configured Sametime or Sametime Premium.
  - Starting and stopping the Sametime server
    Starting and stopping the Sametime server involves starting and stopping the Sametime services running in the container management system.
  - Starting and stopping MongoDB
  - Managing policies
    Sametime policies allows administrators to control user access to features.
    - Policy behaviors
      You can assign anonymous, default, or custom user policies to users or groups to allow or restrict access to certain Sametime features. Sametime uses policy weights and group nesting levels to determine which policies take precedence.
    - Configuring policies
      In previous versions of Sametime there was a graphical user interface available to configure policies. In Sametime 12.0 configuring policies are done in the policies.user.xml file, which is located on the Sametime server.
      - Managing policies on Docker
        This section outlines the steps on how to manage policies in a Docker environment.
      - Managing policies on Kubernetes
        As administrators, you define what end-users can do on a cluster to comply with organization requirements. This section outlines the steps on how to manage policies in a Kubernetes environment.
    - Sametime policy IDs
      This section describes the policies and configurations available in the Sametime deployment.
    - Mobile client policies
      While many user policies are available in the Sametime ecosystem, only a subset of these policies apply to the mobile clients. This section describes the policies and configurations available to the said clients.
    - Changing a user policy’s weight
      Each Sametime policy has a weight assigned to it. The weight should be unique. When assigning a weight to a policy, please ensure the weight is unique on each policy and not duplicated.
    - Assigning users and groups to policies
      Policies can be assigned to users or groups. Policy configuration is done inside the policies.user.xml file.
    - Allowing or restricting custom policies for Sametime clients
      Optionally allow or restrict features for clients by creating exception rules for the policy service in the policyExceptions.xml file.
  - Configuration files
    Configuration files are used to maintain information used by the Sametime server for various reasons. In Sametime v12, configuration files are generated on demand based on information in the container management configuration file based on the whether you are using Docker or Kubernetes.
  - Enabling multi-tenancy
    Multi-tenancy allows multiple organizations to be part of the Sametime community. With multi-tenancy, Sametime users can chat, add users and groups to contact lists, and have awareness of users in their organization or in other organizations that are configured to be visible to them.
  - MongoDB
    This section provides information relating to administering MongoDB.
  - Managing Sametime Meetings
    This topic explains the features you can enable or disable for meetings. Currently, the settings that you can change are global settings that apply to the entire server. User policies cannot control the settings.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Managing policies on Docker

This section outlines the steps on how to manage policies in a Docker environment.

About this task

You can manage your policies on Docker by modifying the following file.

docker-compose.yml

To manage your policies on Docker, follow these steps:

Procedure

Copy the applicable files out of the container.

docker cp <container_name>:/local/notesdata/policies.user.xml .
docker cp <container_name>:/local/notesdata/policies.server.xml .

This step places the files in the current directory.

Locate and edit the policies as necessary.

In the Community section of docker-compose.yml, add a volume reference. Below is an example.

services:
    community:
      image: hclcr.io/st/chat-server:${BUILD_LEVEL}
      restart: ${RESTART_POLICY}
      env_file:
        - custom.env
        - debug.env
      environment:
        - JWT_SECRET_ENV=${JWT_APP_SECRET}
        - DOMINO_SERVER_HOST_ENV=domino
        - DOMINO_SERVER_NAME_ENV=CN\=domino\/O\=test
        - DOMINO_SERVER_DOMAIN_ENV=test
        - ST_BRANDING_INFO_ENV=standard
      volumes:
        - ./policies.user.xml:/local/notesdata/policies.user.xml
      networks:
        - sametime.test
      extra_hosts:
        - "stmobilev12:10.134.102.40"

Restart the server to apply the changes.