Policy planning
You can plan how you want to enable or disable Sametime® instant messaging, meeting, and voice and video features. Use the default policies or create new policies.
Policies manage individual users and groups by enabling or disabling
features for instant messaging, meetings, and voice and video.
- Everyone is assigned to default policies at installation
- You can search for active policies associated with a user
Features you can control through policies:
- Instant messaging:
- Force default server community
- Allow multiple server communities
- Allow Sametime Gateway communities
- Allow people to save chat transcripts
- Limit contact list size
- Allow mobile clients
- Allow custom emoticons
- Allow screen capture
- Restrict image sizes
- Allow file transfer through server
- Allow file peer-to-peer file transfer
- Exclude certain file types from being transferred
- Allow user to install plugins
- Meetings
- Restrict number of meeting rooms per user
- Allow user to create instant, temporary meeting rooms
- Automatically connect to meeting server when logging into Sametime Connect
- Allow search for meeting rooms
- Allow searching for hidden meeting rooms
- Show scheduled meetings
- Allow meetings to be recorded
- Allow meeting room content to be downloaded
- Set meeting room chats to be hidden, read-only, or interactive
- Allow polling
- Allow annotations of uploaded content
- Restrict size of uploads to meeting room library
- Restrict size of library
- Allow screen sharing
- Allow users to take control of another user's shared screen
- Allow peer-to-peer application sharing
- Enforce bandwidth limits
- Voice and Video
- Allow access to third-party service provider capabilities from contact lists, instant messages, and meetings
- Allow changes to preferred numbers
- Allow voice and video, voice only, or no voice and video.
- Allow voice and video in a Web browser
- Allow access to internal audio and video calls
- Set the video resolution for users
Policies are created in the Sametime System Console and stored in DB2®. On startup and every hour, the Sametime Community Servers update the local cache by pulling down the information from the Sametime System Console. The local cache is policies.users.xml stored in the Domino® program directory. It can take up to 2 hours for a policy change to go into effect on a client.