Service account - Introduction and benefits

Service account - Introduction and benefits



Service accounts are usually created specifically for a particular service or application and are granted only the permissions necessary for that service to function properly. They are often used to access other resources such as databases, APIs, file systems, or other services that the application or service needs to interact with. Basically, we use a service account to differentiate the user activity in a  particular application.

Why use a service account to connect the integration applications?

We highly recommend you set up a service email account with a generic name if you wish to avoid using your individual account name on folders/files when the integration syncs folder/file changes to the opposite application. You could set up a user in Procore and SharePoint with an email called syncezy@yourcompany.com for example and use this account to connect Procore and SharePoint in your integration. This will ensure you can easily identify what synced changes our integration has made. Please ensure any new service accounts you set up have full admin permissions on the Documents, Photos, and RFIs tools for all projects you want to sync in Procore and also full read/write permissions on the applicable SharePoint account/sites.

There are several reasons why you might want to use service accounts in your computing environment:

Security: By using service accounts, you can limit the permissions granted to individual applications or services, which helps to reduce the risk of security breaches. Service accounts are typically used for automated processes, they do not require interactive login sessions or access to sensitive information that humans would normally need, such as passwords or other confidential data.

Accountability: When you use service accounts, you can track the actions of individual services or applications, making it easier to identify which system or service is responsible for particular actions or changes within your environment.

Centralization: By using service accounts, you can centralize the management of access and permissions across multiple applications or services, making it easier to ensure that each application has the appropriate level of access and reducing the complexity of managing permissions across your computing environment.


Other questions

Have a support question?

We offer three support channels: 

Chat - Live Chat (24x5 support) from within your integration portal.  

Phone - #1 for Support
AUS: +61 2 9136 9448 
NZ: +64 9 303 2999 
UK: +44 203 670 1109
US: +1 720 500 9302


    • Related Articles

    • Service account - Introduction and benefits

      Service accounts are usually created specifically for a particular service or application and are granted only the permissions necessary for that service to function properly. They are often used to access other resources such as databases, APIs, ...
    • Service account - Introduction and benefits

      Service accounts are usually created specifically for a particular service or application and are granted only the permissions necessary for that service to function properly. They are often used to access other resources such as databases, APIs, ...
    • Creating a Service account in Procore with the right permissions.

      Step-by-step Guide: Creating a Service Account And Selecting the right permissions in Procore. Made by Support Team SyncEzy with Scribe 1. Go to Procore and add a new users. 2. Enter the relevant details here, use SyncEzy in the name so it will make ...
    • Enhancing Security with Google / Microsoft Account Integration and OTP Login

      Enhancing Security with Google / Microsoft Account Integration and OTP Login In our continuous effort to bolster the security and ease of access for our users, SyncEzy is excited to introduce a powerful new security feature designed to streamline ...
    • How to reauthenticate SharePoint with a new or service user?

      How to reauthenticate SharePoint with a new or service user? You may need to change application(s) credentials if an existing user has been archived or due to a change of password. Or it may be, that you would like to use service accounts for your ...