The bind function tells the client to synchronize its local user database with the selected SEP Server of choice.
This means all objects (keys, channels etc) will be stored centrally (not necessarily locally depending on your policy). Adding a server entity to the client’s profile management section will allow the client to use that server as a resource in accessing object when needed. The design allows for having a client working against several SEP-Servers.
What version of SEP client we added auto-bind?
From version: 4.11.12
In the process of binding, the profile automatically inherits any changes or additions to the policies that have been made while working in an "unbound state"; for example, if the password policy got changed locally while being in unbound state, this change will get reflected to the profile centrally as well. To ensure that profile information locally are aligned with information centrally, the SEP-Client will synchronize the bound profile automatically during sign-in.
A bound profile, as well as its SEP Servers will be displayed using bold characters in the list of profiles.