Integrations allow your data to be synchronized with Axify. To do this, they require the use of personal access tokens, which need a certain level of authorization to allow the transfer of information.
Depending on the structure of your organization, you may have certain needs or even questions related to these permissions. Here are some tips to help you manage them.
Feel free to contact us to discuss it!
Create a dedicated Axify user
You're probably familiar with the phrase "divide and conquer", but did you know that this concept can be applied to Axify? Let's take a look at an example.
You are an administrator of your issue management systems (let's take Jira here) and repositories (let's say Gitlab for our example). You could easily generate the access tokens that allow data transfer to Axify. However, these tokens would be dependent on your access and would have the same permission level as you.
A good practice would be to create a new user (for each of the two platforms) that would be dedicated to synchronizing data to Axify. This would allow you to control more precisely the permissions of the generated tokens and this access would be independent of yours, allowing you to detach it from the permission level relative to your access.
We invite you to consult the official documentation of your service providers to learn more about creating users and managing their permissions.
Use a different type of token
Some systems, like Gitlab, allow you to generate access tokens at the project level. This allows, as with the option mentioned above, to break away from individual users and segment the generated token.
Consult the official Gitlab documentation
Manage the validity period of accesses
Many platforms allow you to specify the duration for which a personal access token will be valid. Generally, we recommend selecting the longest validity period when generating personal access tokens to add an integration to Axify. However, you may also need to limit this period for various reasons.
In this kind of situation, it is important to remember that the synchronization of data to Axify depends on the validity of the personal access token. This means that if the token expires, the data will no longer be synchronized to Axify.
We encourage all our users to note the expiration date of the token (in your calendar, for instance) and set a reminder a few days before the end of the period. This will allow you to create a new token and update your configuration to avoid a sync outage.
Don't worry, data synchronization for the process and technical axes is retroactive, so no data will be lost.
Note that some platforms force the expiration of access tokens that have not been used for a certain period of time (e.g. after 1 year, even if the validity period was infinite).