Commit d4f53357 authored by Lukas Eipert's avatar Lukas Eipert

First draft for instance level integration docs

parent 7e7e0bcb
---
stage: Create
group: Ecosystem
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
# Instance level integrations
> Introduced in GitLab 13.3.
Instance level integrations allow you to set up [integrations](../overview.md) for all projects across your instance.
Updating instance level integrations will update all projects inheriting from that integration.
On a project level the instance level integration can be overwritten, in case you want use different settings or disable
a integration.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For an introduction to the feature, see [Instance level integrations walk-through](https://youtu.be/bGq-MH--5BE).
## Setting up an instance level integration
1. Navigate to your Admin Area -> Settings -> Integrations
2. Choose the integration that you want to set up for projects on your instance
3. Fill out the details -> Save
Note: If you set up an instance level integration for the first time, you will set up the same integration for all existing projects that do not have an integration of the same type set up. Projects with an existing integration of the same type are not changed.
## Overwriting an integration on the project level
1. Navigate to your Project -> Settings -> Integrations
2. Choose the integration where you want to overwrite the instance settings.
3. In the dropdown choose: `Use custom settings`
![](./img/instance_level_dropdown.png)
4. Fill out the details -> Save
If you want to switch back to your instance level integration settings, please choose `Use instance level settings`
## Caveats
Instance level integrations are just available for users of self-managed instances. We are currently working on enabling this logic on the group level as well, so that users of GitLab.com can also utilize this feature. [link tba]
Currently it is just possible to inherit the complete settings for an integration. Per-field inheritance is planned. [link tba]
...@@ -80,6 +80,14 @@ all new projects on the instance. ...@@ -80,6 +80,14 @@ all new projects on the instance.
Read more about [Service templates in this document](services_templates.md). Read more about [Service templates in this document](services_templates.md).
## Instance integrations
Instance integrations are a way to control integrations across _all_ projects
of an instance. On the project level you can choose whether to inherit the instance
integration or not.
Read more about [Instance integrations](instance_and_group_integrations.md)
## Troubleshooting integrations ## Troubleshooting integrations
Some integrations use service hooks for integration with external applications. To confirm which ones use service hooks, see the [integrations listing](#integrations-listing) above. GitLab stores details of service hook requests made within the last 2 days. To view details of the requests, go to that integration's configuration page. Some integrations use service hooks for integration with external applications. To confirm which ones use service hooks, see the [integrations listing](#integrations-listing) above. GitLab stores details of service hook requests made within the last 2 days. To view details of the requests, go to that integration's configuration page.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment