> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/permissions-issue-status-code-500.md).
# Permissions Issue: Status Code 500
Discover how to handle situations where fields are inaccessible due to permissions. This issue often arises in integrations with restricted user access, resulting in the fields list not loading in your type mapping configuration. As a result, you may be unable to make changes to the integration. However, Getint offers the ability to customize team access, providing various options based on your preferences.
This problem arises when a user attempts to edit the integration without the necessary permission. To grant editing permissions for connections, the connection owner must authorize all workspace members to make edits. Here's how you can accomplish this:
1. The connection owner should navigate to **Workflows**, select **Connections**, find the connection, and click on the three dots.
2. Click on **Edit**, then proceed by clicking **Next** when prompted.
3. Open the final dropdown menu and select the option **Anyone in the workspace can edit,** then save the connection.
In summary, when fields can't be fetched due to missing permissions, Getint provides customizable team access, allowing the owner to grant editing permissions for connections. This ensures smooth integration management despite permission restrictions. By authorizing all workspace members to edit connections, you maintain flexibility and control over your integrations, enhancing collaboration and productivity within your team.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/permissions-issue-status-code-500.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=7b3ef148-be3a-4b27-9a49-46e5ac13f003)
