
# Connect Azure AD (Entra ID) to Synk.to

<Content>
1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find Azure AD in “Choose a System” field, and click “**Add a System**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/6ef1c8d9-99da-4506-0f10-e3405d025300/public)

2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/1dbd1b72-f5cb-448b-6f0f-c044e8146e00/public)

3. In “**Authentication settings**” choose configuration access type of your connection:
   - **Option 1 - READ**. Provide **read&write** **access** to manage groups, and only **read access** to manage users.
   - **Option 2 - MANAGE (RECOMMENDED)**. Provide **read&write** **access** to users and groups.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/383aa531-c1f0-4b5c-4567-89620aaa0000/public)
</Narrow>
4. Click “**Check connection**”.
5. In a pop-up Microsoft window, sign in using your Azure AD account with **Global Administrator** or **Administrator** role.
   <Narrow>
   ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/e5001cbb-238a-46d1-7cbe-4ecaf49ffb00/public)
   ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/bfa73aa6-d67c-4d4e-c535-3093f302f700/public)
   </Narrow>
6. Click “**Accept**” button on a Microsoft permission pop-up window.
   <Narrow>
   ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c2a54d07-d318-4a2c-926f-b8e0fff09300/public)
   </Narrow>
7. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/dbdc0493-0294-432a-0a19-780b93ee6700/public)
</Narrow>
8. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “[My Connections](https://app.synk.to/connections)” section of Synk.to.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/11b30c80-17ea-48b7-8749-df7895191300/public)
</Content>


Connect Microsoft Azure AD (Entra ID) to Synk.to service to synchronize users and groups. A detailed description of Microsoft Azure AD (Entra ID) connection settings.

# How it works
<Content>
**Synk.to** is the first cloud-first identity management (IDM) platform! This means that you can now integrate multiple software as a service (SaaS) apps into your Synk.to system to seamlessly manage users and groups across your organization.

More and more companies use SaaS systems instead of on-prem solutions. Modern companies estimate that 70% of the business apps that they use today are based on SaaS.

Users and groups synchronization between different SaaS solutions via SCIM protocol is usually available only on SaaS Enterprise plans that cost 2,5x more on average comparing to Pro/Team/Regular SaaS plans.
If you don’t need SaaS Enterprise plans, but need to sync users and groups between SaaS systems, Synk.to is for you!
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/42763393-1ed2-4837-f2b6-9275131aef00/public)
</Narrow>
### Why do I need it?

In 2021, organizations worldwide were using an average amount of 110 software as a service applications (according to [Statista](https://www.statista.com/statistics/1233538/average-number-saas-apps-yearly/)). If you are an admin of such organization, it can be a hassle to keep users and groups in sync across all business SaaS systems. Meanwhile, timely access management is a crucial part of every cybersecurity, privacy and compliance program of every modern organization.

### How it Works?

**Synk.to** connects to different SaaS solutions using regular Admin APIs that usually allow to manage users and groups, but don’t require Enterprise plans.

In order to connect SaaS system to Synk.to you need to provide limited API key or OAuth access. There are usually two types of access that you can provide to Synk.to depending on your needs:

- **Read-write access to manage groups** (add and exclude users from groups) and **read-only access to manage users** in SaaS system. With this type of access Synk.to won’t be able to create, suspend or delete users in SaaS application. But you can still keep your groups in sync across your SaaS solutions.
- **Read-write access to manage groups** (add and exclude users from groups) and **read-write access to manage users** in SaaS system. This type of access is recommended, since only with it you can explore the full power of [Synk.to](http://Synk.to). With this type of access Synk.to will be able to automatically create new users across all your SaaS solutions, terminate or suspend users once they leave your company, and update user info once it changes.

### How can I start?

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/100d0a3e-4e12-436c-0d6b-a479a3b3ff00/public)

In order to start user synchronization you need create account in [Synk.to](http://Synk.to) application and: 

1. Connect at least **two** systems to [Synk.to](http://Synk.to) in “[My Systems](https://app.synk.to/systems)” section of the app. You can find guides on how to connect different SaaS systems to Synk.to [here](https://synk.to/docs/googlews-slack/).
2. Create at least **one** connection in “[My Connections](https://app.synk.to/connections)” section of the app. You can find guide on how to create sync between Google and Slack [here](https://synk.to/docs/googlews-slack/).

The connected system can be either Source System or Replica System:

- **Source System** is a reference system. All user and group changes made in Source System will be replicated to Replica System (in accordance with provided permissions and connection configuration). You should use the primary sources of user and group data in your company as a Source Systems. For example, main HR systems (BambooHR, Zenefits, Lattice) or IdP providers (Google Workspace, Azure AD).
- **Replica System** is a system mimicking user and group changes from Source System.
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/604a8bce-d8a0-4e99-64fa-b3e77634e200/public)
There is one more protection feature build-in to Synk.to is the ability to limit operations with users on a connection level.

- Allow to automatically create new users in the Replica system,
- Allow to automatically deactivate/delete users in the Replica system.

Without that options Synk.to won’t do any critical actions (creation, deletion and suspension) on **users** in Replica System.
<SemiNarrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c10e1edf-3f54-4fc1-d47f-1df7db493a00/public)
</SemiNarrow>
### How can I manage connections?

You can pause the synchronization any time, force connection synchronization (in order not to wait the synchronization interval), view connection log, edit or delete connection.
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/4aac2531-2111-4d6b-c248-10208cde1c00/public)
If you have any questions left, please, check our [FAQ](https://synk.to/docs/faq) or send them to [support@synk.to](mailto:support@synk.to).
</Content>

How it works? Sync cloud groups and users between SaaS systems. Detailed description of Synk.to architecture.

How it works

Sync cloud users and groups - How it works | Synk.to

# How to delegate Google Groups management
<Content>
[Google Groups](https://groups.google.com/my-groups) is a powerful tool that allows organizations to manage communication, collaboration, and information sharing among team members, departments, or project groups. To effectively administer these groups, Google Workspace administrators can delegate Google Groups management to trusted Group Owners (eg. project managers, product team leaders). Delegating these responsibilities can streamline group management and empower group leaders to take ownership of their groups' settings and membership. 

Simultaneously, using [Synk.to](https://synk.to/) platform you can connect these Google Groups to synchronise with dozens of your favourite SaaS systems (eg. Slack, Jira, Confluence, Zoom, etc.). So by delegation Google Workspace administrators will take off much of operational work of not only managing groups, but also managing access to internal business systems.

In this article, we'll explore the step-by-step process of delegating Google Groups management to Group Owners inside your organization.

### Why Delegate Google Groups Management?

Delegating Google Groups management has several advantages:

1. **Efficiency**: Delegating administrative tasks to Group Owners reduces the burden on IT or administrative teams, freeing up their time for more critical tasks.
2. **Empowerment**: Group Owners can make timely decisions related to group membership, permissions, and settings, aligning group management with specific group needs.
3. **Responsiveness**: Group Owners can quickly respond to membership requests, approve or deny requests, and manage group content without requiring central IT intervention.
4. **Streamlined Communication**: Empowering Group Owners fosters better communication within groups, as they can adjust settings and permissions to match their group's unique requirements.
5. **Accountability**: Group Owners will be accountable of their groups, ensuring that they remain active and relevant.

Now, let's dive into the steps to delegate Google Groups management to Group Owners.

### Step 1: Identify Trusted Group Owners

Before you can delegate management responsibilities, identify individuals within your organization who are responsible and trustworthy. Group Owners should be familiar with the group's purpose and willing to take on these additional responsibilities.

### Step 2: Assign Group Owners

1. Log in to your [Google Workspace admin console](https://admin.google.com).
2. Navigate to “**Directory**” → “**Groups**”.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/3e0f88d9-8798-4ab2-7aed-edc27c281d00/public)
    
3. Click on the group for which you want to delegate management.
4. In the group, go to “**Members**” section.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/a29b8e78-bc8d-49ff-44c3-8d930ceb6200/public)
    
5. In the “**Role**” column, choose account of the individuals you want to designate as Group Owners and set “**Owner**” role for them.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/ca47692b-8963-4ca4-fd24-6939e62ae300/public)
    
6. Click “**Save**”.

### Step 3: Communicate with Group Owners

Inform the newly assigned Group Owners about their responsibilities. Encourage open communication to address any questions they may have.

Now they can manage their Google Groups using https://groups.google.com/my-groups link.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b2443359-b99e-4206-48ff-e61706d1c100/public)

In order to add member of the group they need to click on the group, go to “**Members**” section in the left menu, click “**Add members**”, and type new member(s) emails in “**Group members**” field.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/58532b38-46c1-4574-3475-a52d42eef200/public)
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/2cdaf803-3216-4947-9531-8994129bb600/public)
</Narrow>
In order to delete member from the group they need to choose the member and click on “**Remove member**” icon.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/70e6f3af-5a53-484e-9ce3-abd9d3382400/public)

### Step 4: Setup Google Groups synchronization with other SaaS systems

With [Synk.to](https://synk.to/) platform you can connect Google Groups to other groups from dozens of your favourite SaaS systems (eg. Slack, Azure AD, Microsoft 365, Jira, Confluence, Zoom, BambooHR, etc.). 

1. Connect your Google Workspace to Synk.to using [this instruction](https://synk.to/docs/googlews/). 
2. Connect your other SaaS tools to Synk.to and setup Groups mapping between Google Workspace and other SaaS tools:
    1. [Sync Google Workspace and Slack](https://synk.to/docs/googlews-slack/)
    2. [Sync Google Workspace and Microsoft 365](https://synk.to/docs/googlews-ms365/)
    3. [Sync Google Workspace and Azure AD (Entra ID)](https://synk.to/docs/googlews-azure/)
3. Enjoy the power of Synk.to automation during employee group change, on-boarding or termination.

### Conclusion

Delegating Google Groups management to Group Owners can streamline communication, enhance group ownership, and reduce the administrative burden on IT and cybersecurity teams. By following the steps outlined in this article, organizations can empower their Group Owners to take control of their groups, fostering better collaboration and communication within the organization.
</Content>

How to delegate Google Groups management. Sync groups and users between SaaS systems. Detailed description of how to reduce the administrative burden on IT and cybersecurity teams.

Delegate Google Groups management

Sync cloud users and groups - How to delegate Google Groups management | Synk.to

# Sync Google Workspace and Azure AD
<Content>
Prior setting up Google Workspace and Microsoft Azure AD (or Entra ID) users and groups sync you should have Google Workspace and Azure AD (Entra ID) connected in “**[My Systems](https://app.synk.to/systems)**” section of Synk.to application.

If you don’t have them, don’t worry and just follow the following articles first:

- [How to connect Google Workspace to Synk.to](https://synk.to/conectmans/googlews)?
- [How to connect Azure AD (Entra ID) to Synk.to](https://synk.to/conectmans/azuread)?

1. Login to Synk.to and open “[My Connections](https://app.synk.to/connections)” section of the application.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b36a3028-41f1-456b-c4e5-03938626da00/public)

2. Choose Google Workspace as a Source System (which will be used as a reference for users and groups) and Azure AD (Entra ID) as a Replica System (which will receive any users and groups updates made in Source System), and click “**Create Connection**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/64ca7586-903e-476d-5dd3-93df292c0500/public)

3. On a Step 1, set up “**Custom Name**”, sync intervals, “**Connection Description**”, and check the following settings, if you:
    - Allow to automatically create new users in the Replica system,
    - Allow to automatically deactivate/delete users in the Replica system.
    
    Without that settings Synk.to can’t make any critical actions (creation, deletion and suspension) with **users** in Replica System.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/673bad1e-7354-4a62-a6db-d4fbcf6ac200/public)
    </SemiNarrow>
4. Choose Source group and Replica group that you want to keep in sync in terms of users.
5. Check user mapping in the table view. Initially all users are mapped by email and you can’t change that behavior. Use table search to facilitate the mapping.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/44fcfe23-0a37-4e05-da1e-d583e2d3ac00/public)
    </SemiNarrow>
6. (optional) Change “**Action(s)**” from “**To Synk**” to “**To Ignore**” for all users you want to skip from synchronization (eg. service or group users). You can use table search to find all of them.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/666ab01c-c752-4d24-0aad-8a8e9ad5b100/public)
    
7. (optional) Click “**Sync Another Group**” if you want to add more groups in one Connection.
8. Click “**Activate**” to launch users synchronization.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/59c9476b-5e4e-4c24-fb43-778960846200/public)
    </SemiNarrow>
9. Click “**Done**” to finish the connection.

    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/7b6aa08c-6ebf-4e11-7119-919465bdff00/public)
</Content>

Sync your Google Workspace and Microsoft Azure AD (Entra ID) users with Synk.to service. A detailed guide of systems configuration.

Sync Google Workspace and Azure AD

Sync users and groups between Google Workspace and Microsoft Azure AD (Entra ID) with Synk.to

# Sync Google Workspace and Slack
<Content>
Prior setting up Google Workspace and Slack users and groups sync you should have Google Workspace and Slack connected in “**[My Systems](https://app.synk.to/systems)**” section of Synk.to application.

If you don’t have them, don’t worry and just follow the following articles first:

- [How to connect Google Workspace to Synk.to](https://synk.to/docs/googlews/)?
- [How to connect Slack to Synk.to](https://synk.to/docs/slack/)?
<br/><br/>

1. Login to Synk.to and open “[My Connections](https://app.synk.to/connections)” section of the application.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/defe06ad-81e3-4558-606b-ff0b3fbfcc00/public)

2. Choose Google Workspace as a Source System (which will be used as a reference for users and groups) and Slack as a Replica System (which will receive any updates made in Source System), and click “**Create Connection**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/58dc36d7-37d0-4ea7-bbc8-27cce7b31b00/public)

3. On a Step 1, set up “**Custom Name**”, sync intervals, “**Connection Description**”, and choose the following options, if you:
    - Allow to automatically create new users in the Replica system,
    - Allow to automatically deactivate/delete users in the Replica system.
    
    Without that options Synk.to won’t do any critical actions (creation, deletion and suspension) with **users** in Replica System.
    <SemiNarrow>    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/8cb4c44b-dc56-462f-1a90-b3cbb0cde400/public)
    </SemiNarrow>
4. Choose Source group and Replica group that you want to keep in sync in terms of users.
5. Check user mapping in the table view. Initially all users are mapped by email and you can’t change that behavior. Use table search to facilitate the mapping.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/44fcfe23-0a37-4e05-da1e-d583e2d3ac00/public)
    </SemiNarrow>
6. (optional) Change “**Action(s)**” from “**To Synk**” to “**To Ignore**” for all users you want to skip from synchronization (eg. service or group users). You can use table search to find all of them.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/666ab01c-c752-4d24-0aad-8a8e9ad5b100/public)
    
7. (optional) Click “**Sync Another Group**” if you want to add more groups in one Connection.
8. Click “**Activate**” to launch users synchronization.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/59c9476b-5e4e-4c24-fb43-778960846200/public)
    
9. Click “**Done**” to finish the connection.
</Content>


Sync your Google Workspace and Slack users with Synk.to service. A detailed guide of systems configuration.

Sync Google Workspace and Slack

Sync users and groups between Google Workspace and Slack with Synk.to

# Sync Google Workspace with Microsoft 365 and Teams
<Content>
Prior setting up Google Workspace and Microsoft 365 Admin Center users and groups sync you should have Google Workspace and Azure AD (yes, that’s right. Azure AD (or Entra ID) and Microsoft 365 Admin Center have the same API) connected in “**[My Systems](https://app.synk.to/systems)**” section of Synk.to application.

If you don’t have them, don’t worry and just follow the following articles first:

- [How to connect Google Workspace to Synk.to](https://synk.to/conectmans/googlews)?
- [How to connect Azure AD (Entra ID) to Synk.to](https://synk.to/conectmans/azuread)?

1. Login to Synk.to and open “[My Connections](https://app.synk.to/connections)” section of the application.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b36a3028-41f1-456b-c4e5-03938626da00/public)

2. Choose Google Workspace as a Source System (which will be used as a reference for users and groups) and Azure AD (Entra ID) as a Replica System (which will receive any users and groups updates made in Source System), and click “**Create Connection**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/64ca7586-903e-476d-5dd3-93df292c0500/public)

3. On a Step 1, set up “**Custom Name**”, sync intervals, “**Connection Description**”, and check the following settings, if you:
    - Allow to automatically create new users in the Replica system,
    - Allow to automatically deactivate/delete users in the Replica system.
    
    Without that settings Synk.to can’t make any critical actions (creation, deletion and suspension) with **users** in Replica System.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/673bad1e-7354-4a62-a6db-d4fbcf6ac200/public)
   </SemiNarrow>
4. Choose Source group and Replica group that you want to keep in sync in terms of users. Both Azure AD ([Security groups](https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/how-to-manage-groups)) and [Microsoft 365 groups](https://admin.microsoft.com/#/groups) will be in the list. Microsoft 365 groups have special description under the group name. [Learn more about Microsoft 365 group types](https://learn.microsoft.com/en-US/microsoft-365/admin/create-groups/compare-groups). 
If Microsoft 365 group is [Microsoft Teams enabled group](https://learn.microsoft.com/en-US/microsoftteams/user-access), the user will be automatically added to the corresponding Microsoft Teams channel after synchronization. **Note**: Teams licensing plan (for example, Microsoft 365 Enterprise E3 or Microsoft 365 Business Premium) should be assigned to a user and the user is should be enabled for Teams prior synchronization.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/11755cd9-8e4e-4240-a705-b38110935d00/public)
<SemiNarrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/86d8f537-1e17-481c-274e-a760a402a300/public)
</SemiNarrow>
5. Check user mapping in the table view. Initially all users are mapped by email and you can’t change that behavior. Use table search to facilitate the mapping.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/44fcfe23-0a37-4e05-da1e-d583e2d3ac00/public)
    </SemiNarrow>
6. (optional) Change “**Action(s)**” from “**To Synk**” to “**To Ignore**” for all users you want to skip from synchronization (eg. service or group users). You can use table search to find all of them.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/666ab01c-c752-4d24-0aad-8a8e9ad5b100/public)
    
7. (optional) Click “**Sync Another Group**” if you want to add more groups in one Connection.
8. Click “**Activate**” to launch users synchronization.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/59c9476b-5e4e-4c24-fb43-778960846200/public)
    
9. Click “**Done**” to finish the connection.

    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/7b6aa08c-6ebf-4e11-7119-919465bdff00/public)
</Content>

Sync your Google Workspace and Microsoft 365 and Microsoft Teams users and groups with Synk.to service. A detailed guide of systems configuration.

Sync Google Workspace and MS 365

Sync users and groups between Google Workspace and Microsoft 365 Admin Center with Synk.to

Connect | Azure AD (Entra ID)

Connect Microsoft Azure AD (Entra ID) to Synk.to

# Connect BambooHR to Synk.to
<Content>
### **Step 1**: **Create API token from your BambooHR account**

1. **Log in** to your BambooHR account using administrator credentials.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/e7d770db-1538-4a2d-dfa5-eab8134ef500/public)
    </Narrow>
2. Click on your profile top right icon and choose “**API Keys**” in the menu.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/8a0bd526-d337-422c-976a-85c8d6cc8500/public)
    
3. Click “**Add New Key**”.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f52ee826-995b-4553-6279-8f52a24aef00/public)
    
4. In the opened window enter "**synkto**" as the API Key Name for your token and click “**Generate Key**”.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/44f27bd6-c237-47fb-b263-19a021453800/public)
    </SemiNarrow>
5. Click “**Copy Key”** and save the **API key,** and click “**Done**”. Note that for security reasons it isn't possible to view the token after closing the dialog. If necessary, create a new token.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/30922b24-6d1a-4ce0-3f95-3709f50db700/public)
    </SemiNarrow>
6. Get your **BambooHR site URL** ready. It should look like: [https://your-domain.bamboohr.com](https://your-domain.bamboohr.com/)

### Step 2. Connect BambooHR to Synk.to

1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find BambooHR in “Choose a System” field, and click “**Add a System**”.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/ba4caf1b-0c89-475f-9f3c-23ec04e92500/public)
    
2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/70de5d14-1a52-4d07-ea93-de41bb5dac00/public)
    
3. In “**Authentication settings**” provide your “**BambooHR site URL**”, and “**API Token**” from Step 1 of the guide.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/29491b7c-8c05-4e3f-56f9-c51e9dcad100/public)
    </Narrow>
4. Click “**Check connection**”. 
5. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f792a8b2-54f1-47db-6872-c1a9af9f2800/public)
    </Narrow>
6. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “My Connections” section of Synk.to.
    <SemiNarrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/565f1ab7-446a-44dd-73ec-b1024f366900/public)
    </SemiNarrow>
</Content>

Connect BambooHR to Synk.to service to synchronize users and groups. A detailed description of BambooHR connection settings.

Connect | BambooHR

Connect BambooHR to Synk.to

# Connect Confluence Cloud to Synk.to
<Content>
### **Step 1**: **Create an [API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) from your Atlassian account**

1. **Log in** to your [Atlassian account](https://id.atlassian.com/manage-profile) with account that have “**Administer Jira**” [global permission](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/).

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b7818635-91f2-4762-232b-0a274c375800/public)

2. Go to **Security** → “[Create and manage API tokens](https://id.atlassian.com/manage-profile/security/api-tokens)” or just click [https://id.atlassian.com/manage/api-tokens](https://id.atlassian.com/manage/api-tokens).

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/9bd2d8e1-35aa-44c6-3328-2486acfc2b00/public)

3. Click **Create API token**.
4. From the dialog that appears, enter "**SynkTo**" as the **Label** for your token and click **Create**.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/d6f5e23b-d9bb-4844-ab6e-f30df2362600/public)

5. Click **Copy** and save the **API token**. Note that for security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/0f58891e-7ab0-4add-4759-45f8ac58df00/public)

6. Get your **Confluence Cloud site URL**. It should look like: [https://your-domain.atlassian.net](https://your-domain.atlassian.net/)

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/041b6c2c-b455-4ab1-a5e5-4bf3625cb000/public)

### Step 2. Connect Confluence Cloud to Synk.to

1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find **Confluence Cloud** in “Choose a System” field, and click “**Add a System**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c4fa5194-848a-42d7-c7c6-6ec57564ed00/public)

2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/ca840c32-e245-40f7-f48d-c348d5d3e300/public)
</Narrow>
3. In “**Authentication settings**” provide your “**Atlassian account email address**”, “**Confluence site URL**”, and “**API Token**” from Step 1 of the guide.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/3b7d9118-e6b9-405f-25ca-944f16dfb700/public)
</Narrow>
4. Click “**Check connection**”. 
5. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/3b7d9118-e6b9-405f-25ca-944f16dfb700/public)
</Narrow>
6. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “My Connections” section of Synk.to.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/192f1a96-6ad0-4888-4b5b-6592f66cac00/public)
</Content>

Connect Confluence Cloud to Synk.to service to synchronize users and groups. A detailed description of Confluence Cloud connection settings.

Connect | Confluence Cloud

Connect Confluence Cloud to Synk.to

# Connect Google Workspace to Synk.to
<Content>
1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find **Google Workspace** in “Choose a System” field, and click “**Add a System**”.
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/98325e4c-7d83-4085-c9f4-c9ae47b44d00/public)
2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/18e6835d-fdab-45f1-677b-71a553bf3a00/public)

3. In “**Authentication settings**” choose configuration access type of your connection:
    - **Option 1 - READ**. Provide **read&write** **access** to users and groups.
    - **Option 2 - MANAGE (RECOMMENDED)**. Provide **read&write** **access** to manage groups, and only **read access** to manage users.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/467428eb-2182-4dbf-0a07-69ba9740c200/public)
</Narrow>
4. Click “**Check connection**”. 
5. In a pop-up Google window, sign in using your Google Workspace **administrator** account.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f95e581c-9154-472d-d4c4-89153bf36800/public)
</Narrow>
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/5b432af4-3fc7-4384-e010-091d5220fb00/public)
</Narrow>
6. Click “**Allow**” on a Google OAuth pop-up window.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/539e3369-3d0a-4049-3058-551bcbca5b00/public)
</Narrow>
7. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/6b331bde-23fe-40e9-0021-351b420b6600/public)
</Narrow>
8. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “My Connections” section of Synk.to.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/2c222348-23b8-459a-96ca-d478ccc59000/public)
</Content>


Connect Google Workspace to Synk.to service to synchronize users and groups. A detailed description of Google Workspace connection settings.

Connect | Google Workspace

Connect Google Workspace to Synk.to

# Connect Jira Cloud to Synk.to
<Content>
### **Step 1**: **Create an [API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) from your Atlassian account**

1. **Log in** to your [Atlassian account](https://id.atlassian.com/manage-profile) with account that have “**Administer Jira**” [global permission](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/).

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b7818635-91f2-4762-232b-0a274c375800/public)

2. Go to **Security** → “[Create and manage API tokens](https://id.atlassian.com/manage-profile/security/api-tokens)” or just click [https://id.atlassian.com/manage/api-tokens](https://id.atlassian.com/manage/api-tokens).

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/9bd2d8e1-35aa-44c6-3328-2486acfc2b00/public)

3. Click **Create API token**.
4. From the dialog that appears, enter "**SynkTo**" as the **Label** for your token and click **Create**.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/d6f5e23b-d9bb-4844-ab6e-f30df2362600/public)

5. Click **Copy** and save the **API token**. Note that for security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/0f58891e-7ab0-4add-4759-45f8ac58df00/public)

6. Get your **Jira Cloud site URL**. It should look like: [https://your-domain.atlassian.net](https://your-domain.atlassian.net/)

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/e7681153-33da-42a0-cd26-b8cb514af000/public)

### Step 2. Connect Jira Cloud to Synk.to

1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find **Jira** in “Choose a System” field, and click “**Add a System**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/2c804565-16a4-4d71-b2ec-343c40240300/public)

2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/fcec82c6-7086-4272-9155-015c9254be00/public)

3. In “**Authentication settings**” provide your “**Atlassian account email address**”, “**Jira site URL**”, “**API Token**” from Step 1 of the guide, and “**Jira project name**” (the list of the projects can be found at [https://your-domain.atlassian.net/jira/projects](https://your-domain.atlassian.net/jira/projects)).
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/bae057b8-4e64-4163-7448-242c396e3700/public)
</Narrow>
4. Click “**Check connection**”. 
5. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b3e1694d-66ea-48fa-adc2-ee1eb7f57700/public)
</Narrow>
6. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “My Connections” section of Synk.to.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b85f8a0c-a19e-4b13-68b5-669c49495d00/public)
</Content>

Connect Jira Cloud to Synk.to service to synchronize users and groups. A detailed description of Jira Cloud connection settings.

Connect | Jira Cloud

Connect Jira Cloud to Synk.to

# Connect Slack to Synk.to
<Content>
### **Step 1**: Create Slack application for Synk.to

1. Go to [https://api.slack.com/apps](https://api.slack.com/apps) using Slack Workspace Owner or Admin user account.
2. Click “**Create New App**” green button.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/d95cb19b-824d-4c03-0f84-9b4903c12200/public)

3. Choose “**From an app manifest**”.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/7cc02b21-0a51-4d1f-6af3-614440980c00/public)
</Narrow>
4. (optional - if you have access to multiple Slack Workspaces) Pick a target workspace you want to provide access to and click “**Next**”.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/169c4ea5-161e-4d6d-8a78-73d5e2c6ab00/public)
</Narrow>
5. Copy the following JSON Slack application manifest, paste it into the JSON window, and click “**Next**” (please check “List of User Scopes” section for additional details below).
    - **Option 1 (RECOMMENDED)**. Provide **read&write** **access** to users and groups.
    
    ```jsx
    {
        "display_information": {
            "name": "Synk.to APP RW"
        },
        "oauth_config": {
            "redirect_urls": [
                "https://app.synk.to/systems/auth/slack/callback"
            ],
            "scopes": {
                "user": [
                    "admin",
                    "groups:read",
                    "groups:write", 
                    "users.profile:read",
                    "users.profile:write",
                    "users:read",
                    "users:read.email"
                ]
            }
        },
        "settings": {
            "org_deploy_enabled": false,
            "socket_mode_enabled": false,
            "token_rotation_enabled": true
        }
    }
    ```
    
    **What will Synk.to app be able to view and do with Option 1 app?**
    
    - View profile details about people in your workspace 
    - View information about your identity
    - View user groups in your workspace
    - View email addresses of people in your workspace
    - View people in your workspace
    - Edit your profile information and status
    - Create and manage user groups
    - Administer your workspace
    
    - **Option 2**. Provide **read&write** **access** to manage groups, and only **read access** to user management.
    
    ```jsx
    {
        "display_information": {
            "name": "Synk.to APP RO"
        },
        "oauth_config": {
            "redirect_urls": [
                "https://app.synk.to/systems/auth/slack/callback"
            ],
            "scopes": {
                "user": [
                    "groups:read",                
                    "groups:write",
                    "users.profile:read",
                    "users:read",
                    "users:read.email"
                ]
            }
        },
        "settings": {
            "org_deploy_enabled": false,
            "socket_mode_enabled": false,
            "token_rotation_enabled": true
        }
    }
    ```
    
    **What will Synk.to app be able to view and do with Option 2 app?**
    
    - View profile details about people in your workspace
    - View information about your identity
    - View user groups in your workspace
    - View email addresses of people in your workspace
    - View people in your workspace
    - View your profile information and status
    - Create and manage user groups
<Narrow>    
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/068ee947-bb6d-4b22-97de-f7ede0aae400/public)
</Narrow>
6. Click “**Create**”.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c7fdd13c-7cb7-4a8c-d23e-322d9289a100/public)
</Narrow>
7. In the application window copy your “**Client ID**” and “**Client Secret**” in “**Basic Information**” → “**App Credentials**” section. You will need them for Synk.to connection.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c1752547-a27c-40f3-35b5-6ac89f88a800/public)

### **Step 2**: Connect Slack to Synk.to

1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find **Slack** in “Choose a System” field, and click “**Add a System**”.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/d260ce2d-136b-4526-8c01-da437ed0e200/public)

2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/23c4d9fe-e10e-4600-83b7-b133318a8e00/public)

3. In “**Authentication settings**” provide your “**Client ID**” and “**Client Secret**” from Step 1 of the guide.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/2d0bfe1f-736e-465f-e065-343a1368b300/public)
</Narrow>
4. Click “**Check connection**”. 
5. In a pop-up Slack window, click “**Allow**”.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/83f1003c-d705-475d-92b3-2ad063328a00/public)
</Narrow>
6. If everything is fine, you will see “**Account Connected**” green mark and the number of users and groups in the system in the bottom.
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/52dbd843-424a-40f1-e927-7d78d312f200/public)
</Narrow>
7. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “My Connections” section of Synk.to.

![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/6289f6b1-30b6-49c3-b633-6d607173dc00/public)

### List of User Scopes required by Synk.to Slack app

1. **[admin](https://api.slack.com/scopes/admin)** (only for Option 1 extended access)
    1. **Why do we need it?** New user account activation and deactivation.
2. **[groups: read](https://api.slack.com/scopes/groups:read)**
    - **Why do we need it?** View basic information about user groups in your Slack Workspace.
    - **Methods we use:**
        - c*onversations.list*
        - users.conversations
3. **[groups: write](https://api.slack.com/scopes/groups:write)**
    - **Why do we need it?** Manage user groups in your Slack Workspace.
    - **Methods we use:**
        - c*onversations.list*
        - users.conversations
4. **[users.profile: read](https://api.slack.com/scopes/users.profile:read)** 
    - **Why do we need it?** Read a user’s profile information and status.
    - **Methods we use:**
        - c*onversations.list*
        - users.conversations
5. **[users.profile: write](https://api.slack.com/scopes/users.profile:write)** (only for Option 1 extended access)
    - **Why do we need it?** Edit a user’s profile information (eg. first and last names) and status.
    - **Methods we use:**
        - c*onversations.list*
        - users.conversations
6. **[users: read](https://api.slack.com/scopes/users:read)**
    - **Why do we need it?** Get a user list to add them to the database.
    - **Methods we use:**
        - u*sers.list*
    - **Events we use:**
        - u*ser_profile_changed*
        - t*eam_join*
7. **[users: read.email](https://api.slack.com/scopes/users:read.email)**
    - **Why do we need it?** View user’s email.
    - **Methods we use:**
        - users.lookupByEmail
</Content>

Connect Slack to Synk.to service to synchronize users and groups. A detailed description of Slack connection settings.

Connect | Slack

Connect Slack to Synk.to

# Connect Zoom to Synk.to
<Content>
### **Step 1**: Create Zoom application for Synk.to
1. Login to [https://zoom.us/signin](https://zoom.us/signin#/login) using Zoom Workspace Owner or Admin user account.
2. Go to https://marketplace.zoom.us/develop/create and click “**Create**” for **Server-to-Server OAuth** app.
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/5f3d908e-257b-4b0e-d37b-8b1d18254900/public)
3. In “**Create a Server-to-Server OAuth app**” pop-up window type “Synk.to” as App Name.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f4aae44c-c239-4746-010b-a6719dcf8f00/public)
    </Narrow>
4. In the “**App Credentials**” section copy your “**Account ID**”, “**Client ID**”, and “**Client Secret**”. You will need them for Synk.to connection.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/67cd88c9-7708-4d97-4cb2-529ee4708700/public)
    
5. Click “**Continue**”.
6. In the “**Information**” section fill in “Short Description”, “Company Name”, developer “Name” and developer “Email”.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f2fdce0b-5955-433f-3499-2a1632707400/public)
    
7. In the “**Scopes**” section click “**+Add Scopes**” button.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/bb34027c-7748-4cfc-9089-fe6033ab0100/public)
    
8. In “**Add scopes**” window click on “**User**” section and choose “**View users information and manage users**” first. After that click on “**Group**” section, choose “**View and manage groups**”, and click “**Done**”. Synk.to needs this permission to sync users and groups.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/abf7b24c-6518-40dc-ad85-97ffdb0a0f00/public)
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/8e5e1a0c-9b55-4fbf-6275-e70e352ce300/public)
    
9. Click “**Continue**”.
10. In the last “**Activation**” section click “**Activate your app**” button.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/653b4795-3901-4437-9ef1-af5300ae2100/public)
    
11. You should see “**Your app is activated on the account**” message after successful activation.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/2d99283b-1f02-4fdc-18e1-874631803400/public)
    
### **Step 2**: Connect Zoom to Synk.to
</br>
1. Go to the [SynkTo Systems](https://app.synk.to/systems) page, find Zoom in “Choose a System” field, and click “**Add a System**”.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/f1cd5271-d11a-47be-f692-d0bd7534fa00/public)
    
2. Provide “**Custom Name**” and “**Description**” to the system in order to remember it. It will be used in “My Connections” section.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/b8f84df0-9c43-43ac-5baf-ecf1e4251f00/public)
    
3. In “**Authentication settings**” provide your “**Account ID**”, “**Client ID**”, and “**Client Secret**” from the Step 1 of this instruction.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/569c70ba-9c0c-4b4b-d38f-125b42da3200/public)
    </Narrow>
4. Click “**Check connection**”.
5. If everything is fine, you will see “**Account Connected**” green mark and the number of system users and groups in the bottom.
    <Narrow>
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/9d2a1e92-dd75-4b20-9a07-a26ea48ec100/public)
    </Narrow>
6. Click “**Save**” and you will see the system in My Systems list. Congrats!!! Now you can use it in “**My Connections**” section of Synk.to.
    
    ![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/c227c67c-4fd5-4c09-456d-20e80ae8d900/public)
</Content>

Connect Zoom to Synk.to service to synchronize users and groups. A detailed description of Zoom connection settings.

Connect | Zoom

Connect Zoom to Synk.to

# Security and Reliability
<Content>
Synk.to is committed to protection and due use of customer data. Our platform is designed to ensure the privacy and security of our platform end users. As a company committed to the security of our client's data, we implement and maintain the following physical, administrative and technical controls to safeguard data while in transit and at rest. 
<Narrow>
![Untitled](https://imagedelivery.net/n1rr2Tp1Rn85NS5EY9zYRA/e6461865-8fac-4bca-7fa1-96ae7b98ea00/public)
</Narrow>

### **1. Security Program and Policies**

1.1 Synk.to maintains and enforces a risk-based security program and framework that addresses how we manage security.  Synk.to’s security framework is based on the ISO 27001 Information Security Management System and includes the following areas: Policies and Procedures, Asset Management, Access Management, Cryptography, Physical Security, Operations Security, Communications Security, Business Continuity Disaster Recovery Security, People Security, Product Security, Cloud and Network Infrastructure Security, Security Compliance, Third-Party Security, Vulnerability Management, and Security Monitoring and Incident Response.

1.2 Our security program includes:

- documented policies that we approve, publish and communicate to appropriate personnel internally and review at least annually,
- documented, clear assignment of responsibility and authority for security program activities,
- regular testing of the key controls, systems and procedures.

### **2. Risk and Asset Management**

2.1 Synk.to utilizes an integrated risk management approach with a focus on both technical and operational security practices. Ongoing and systematic risk assessment is a consistent part of selecting appropriate improvement protection controls and ensuring that Personal Data is safe.

2.2 Synk.to takes reasonable actions to identify assets and their level of criticality. The full inventory and categorization are the basis to select and implement optimal technical and organizational security measures to make sure that the assets and information are protected.

### **3. Personnel security and awareness**

3.1 Synk.to’s personnel (employees and contractors) do not process Personal Data without authorization. Personnel isare obligated to maintain the confidentiality of any Personal Data and this obligation continues even after their engagement ends.

3.2 Synk.to’s personnel (employees and contractors) acknowledge their data security and privacy responsibilities under Synk.to’s policies.

3.3 Synk.to is focused on employee security awareness as a key driver to improve overall security maturity level and culture. Synk.to’s personnel (employees and contractors) conduct security and privacy training at least annually.

### **4. Access Management**

4.1 Synk.to manages access based on “Need to know” and “Least privilege” principles. That means that personnel is only permitted to have access to customer data when needed for the performance of their functions.

4.2 Synk.to deactivates the authentication credentials of personnel immediately upon the termination of their employment or services.

4.3 In order to access the production environment and critical systems, a user must have a unique username and password and multi-factor authentication enabled.

4.4 Synk.to implements measures to prevent information systems from being used by unauthorized persons, including the following measures (a) user identification and authentication procedures; (b) unique username/password (c) password complexity policies (special characters, minimum length, change of password) (c) automatic blocking (e.g., password or timeout).

4.5 Synk.to performs access monitoring and logging for the production environment and critical systems.

### **5. Technical and Application Security Measures**

5.1 Synk.to has implemented and will maintain appropriate technical and application security measures, internal controls, and information security routines intended to protect Personal Data against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows:

- **Segregation of environments**. Synk.to segregates development and production environments to make sure that Personal Data is protected from any kind of unauthorized access.
- **Encryption in transit.** All external network communications are protected with encryption. We support the latest recommended secure cipher suites to encrypt all traffic in transit, including the use of TLS 1.2 protocols, AES256 encryption, and SHA2 hash functions, whenever supported by the clients.
- **Encryption at rest.** Customer data at rest is encrypted using FIPS 140-2 compliant encryption standards, which applies to all types of data at rest within Synk.to’s systems—relational databases, file drives, backups, etc. Access to cryptographic keys is restricted to a limited number of authorized Synk.to personnel.
- **Redundancy**. Synk.to selects IT Infrastructure suppliers that are committed to provide mechanisms with builtd-in security best practices for confidentiality, integrity, and availability. Synk.to’s main IaaS provider AWS is committed to meet the strict Disaster Recovery (DR) Service Level Agreement.
- **Vulnerability assessment**. Synk.to performs automated and manual application and infrastructure security testing to identify and patch potential security vulnerabilities. Critical software patches are evaluated, tested, and applied proactively.
- **Penetration Testing**. We engage independent service providers to perform penetration tests to assess the potential system security threats at least on an annual basis.
- **Software Development and Acquisition**. Synk.to follows security- by- design principles across different phases of the Service creation lifecycle from requirements gathering and product design all the way through product deployment. For the software developed by Synk.to, Synk.to follows secure coding standards and procedures set out in its standard operating procedures.
- **Storage.** Synk.to’s production databases and data processing servers are hosted in a data center located in AWS. Synk.to maintains complete administrative control over the databases and virtual servers, and no third-party vendors have logical access to Personal Data.
- **Change Management.** Synk.to implements documented change management procedures that provide a consistent approach for controlling, implementing, and documenting changes (including emergency changes) for Synk.to’s software, information systems or network architecture.
- **Network security.** All network access between servers is restricted, using access control lists to allow only authorized services to interact in the network. We utilize third-party tools to detect, mitigate, and prevent Distributed Denial of Service (DDoS) attacks.

### **6. Third-Party Provider Management**

6.1 Synk.to may use third- party providers to provide the Services. In selecting third- party providers who may gain access to, store, transmit or use Personal Data, Synk.to conducts a quality and security assessment pursuant to the provisions of its standard operating procedures.

6.2 Synk.to enters into written agreements with all of its providers which include confidentiality, privacy, and security obligations that provide an appropriate level of protection for Personal Data that these providers may Process.

### **7. Physical and Environmental Security**

7.1 Synk.to uses AWS data centers to host its production infrastructure. AWS data centers are strictly controlled both at the perimeter and at building ingress points by professional security staff utilizing video surveillance, intrusion detection systems, and other electronic means. Each data center has redundant electrical power systems that are available twenty-four (24) hours a day, seven (7) days a week.

7.2 Synk.to reviews third-party audit reports to verify that Synk.to’s service providers maintain appropriate physical access controls for the managed data centers.

### **8. Resilience and Service Continuity**

8.1 Synk.to implements measures to ensure the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident, including:

- Ongoing Personal Data backup procedures. Backups are retained redundantly across multiple availability zones and encrypted in transit and at rest.
- Synk.to uses specialized tools to monitor the Service performance. The alert is triggered in the event of any suboptimal server performance or overloaded capacity.
- Disaster recovery plans are in place to recover in case of Personal Data availability issues.

### **9. Information Security Incident Management**

9.1. Synk.to implements security incident management policies and procedures that address how we manage Data Breach and other security incidents.

9.2. In case of Data Breach Synk.to will promptly investigate the incident upon discovery. To the extent permitted by applicable law, Synk.to will notify Customer of a  Data Breach. Data Breach incident notifications will be provided to Customers via email or in the other way agreed with Customer.
</Content>

Security and reliability information of Synk.to service. Check how Synk.to protects your data.

Security & Reliability

Security and reliability | Synk.to

# FAQ
<Content>
### General

- **Why do I need Synk.to?**
    
    **Synk.to** is the first cloud-first identity management (IDM) platform! This means that you can now integrate multiple software as a service (SaaS) apps into your Synk.to system to seamlessly manage users and groups across your organization.
    
    More and more companies use SaaS systems instead of on-prem solutions. Modern companies estimate that 70% of the business apps that they use today are based on SaaS.
    
    Users and groups synchronization between different SaaS solutions via SCIM protocol is usually available only on SaaS Enterprise plans that cost 2,5x more on average comparing to Pro/Team/Regular SaaS plans.
    
    If you don’t need SaaS Enterprise plans, but need to sync users and groups between SaaS systems, Synk.to is for you!
    
- **What is Source system?**
    
    Source system is a reference system for users and groups to be synced to Replica Systems. Usually it is the first system where your users appear. It can be Google Workspace, Azure AD (Entra ID) or some HR system (BambooHR, Zenefits, etc.).
    
- **What is Replica system?**
    
    Replica system is some third-party SaaS solution that should receive any changes made in Source system. Some good examples of replica systems are issue tracking tools (eg. Jira Cloud or Asana), communication tools (eg. Slack or Microsoft Teams), code repositories (eg. GitLab or Bitbucket) and other SaaS business systems.
    
- **If I make a change in Source or Replica system, when is it reflected in Synk.to?**
    
    If you open Source and Replica connection settings, you can see changes immediately with Current Status and upcoming action for each user for a next sync cycle. Users and groups will be synchronization in Replica systems in accordance with sync interval set in Connection Details. Due to rate limits on SaaS APIs, 15 minutes is the lowest interval you can set for synchronization.
    
- **Can I exclude certain users from sync?**
    
    Sure, just move them to “To Ignore” state in “Group Mapping” tab of your connection settings. This is especially relevant, if you have technical, testing or service accounts in your groups. You will need to set it up for every group mapping you have.
    

### Billing

- **How much does Synk.to cost?**
    
    We have Free plan, which gives you access to all our features, but limits sync functionality only for up to 100 users and 3 groups. The Pro plan has flat pricing of $2 synced user per month (including VAT).
    
    For more information on our plans, check out our [pricing page](https://synk.to/#special_pricing).
    
- **What happens if I reached the limit on Free and don't go to Pro?**
    
    Once the threshold of 100 synced users is reached, no other new users will be synced above the threshold. The first 100 users will be kept in sync.
    
    If you reach 3 groups limit, no other groups/connections will be allowed to add. But you can still delete some old one and add new to meet the Free plan limit. 
    
- **How do you count synced users for billing?**
    
    The charge is calculated for the number of users (excluding users in “To Ignore” state) in connected groups of Source Systems you have in a given month at a billing date/time. You can check the number of users synced in a billing month on the main [dashboard](https://app.synk.to/dashboard) of your Synk.to account.
    
    The metered billing user count is calculated 2 days ahead of the next billing date. The billing notification email is sent to your account email, so you can be aware of the upcoming charge.
    
- **Is there a free trial period?**
    
    We don’t offer free trial period. If you want to test our solution, please, use our Free plan.
    
- **How can I upgrade to Pro?**
    
    You can upgrade to Pro plan by going to “[Subscription](https://app.synk.to/profile/subscription)” tab in “Profile & Settings” section of your Synk.to account, and choosing “Select Plan” in Pro Plan section. You will be redirected to Paddle payment system, where you should attach credit card to your Synk.to account. You will be billed upon upgrade from the Free plan to Pro plan.
    
- **How do I cancel my subscription?**
    
    You can downgrade your plan by going to “[Subscription](https://app.synk.to/profile/subscription)” tab in “Profile & Settings” section of your Synk.to account, and choosing “Downgrade” in Free Plan section. If you are on Pro plan and has less than 100 users and less that 3 groups, we will still bill your account.
    
- **What will happen to my connections if I cancel Pro subscription?**
    
    They will be kept in your account, but synchronization will be working only within Free plan limits.
    
- **Can I pay annually?**
    
    No, currently we don’t support annual payments.
    
- **What will happen if my payment fails?**
    
    If our first attempt to automatically charge your account fails, we try again in 24 hours. And will try for the next 5 days. After that your service will be suspended.
    

### System and features support

- **What system integrations do you support?**
    
    Currently we support Google Workspace, Slack, and Jira Cloud.
    
    For Slack connection, note that creation, suspension and deletion of users are only supported on Slack Business+ plan.
    
- **What systems do you plan to support in future?**
    
    We will support more and more SaaS solutions in the upcoming months. Currently we are working on adding Microsoft Teams, Jira Enterprise and BambooHR support. 
    
- **There is an integration or feature I want, but don't see in Synk.to. Can I request it?**
    
    Sure, we are continuously develop our product and eager to hear the requirements of our users. You can submit your request using “**[Contact Us](https://synk.to/#contact-us)**” form on our landing page. We will evaluate it, and if it fits our product strategy, we will integrate it free of charge.
    
- **How do I sign up to hear about new functionality?**
    
    Just sign in to our service and we will let you know about our product updates.

</Content>

We tried to answer frequently asked questions about users and groups sync between cloud systems with Synk.to