![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
Hypersyncs can be created via a user's app credentials OR via a service account (recommended).
Using personal app credentials
A Hyperproof user may already have personal credentials for an application. These credentials can be used to establish a connection for Hypersyncs without requiring involvement from IT. This makes it easy to get started, but is NOT recommended long term. For long term continuity and maintainability, it’s recommended to use service accounts set up by your IT department.
Using a service account
A service account is a set of credentials created by your IT admin that can be used by multiple proof collectors in your organization. Rather than each user creating and managing Hypersyncs with their own login credentials (e.g. [email protected]), they’ll use the same set of credentials to manage their own Hypersyncs (e.g. [email protected]).
Sharing connections
Members can be added to a single Hypersync connection and assigned roles that allow them to manage the membership and properties of the connection versus only being able to use the connection to create Hypersyncs. Users automatically see connected apps that they’ve been added to and are a member of.
Manager versus viewer
Managers can add members to the connection and change their role.
A manager who is also the owner of the Hypersync can add members, change roles, and adjust the Hypersync’s settings, e.g. how often proof is collected. This individual can also update the shared credentials if needed.
Managers can create a new Hypersync via the shared connection.
Viewers cannot add members to the connection or change member roles.
Viewers cannot adjust settings.
Viewers can create a new Hypersync via the shared connection.