> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/citation-access-after-permission-changes.md).

# Citation Access After Permission Changes

Changing file permissions can affect new retrieval and existing citation links differently. Review both paths when access is removed.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FLNlku9OwAOEBMKC1Z2AR%2Fcitation-access-after-permission-changes.mp4?alt=media&token=17f4150c-eae6-44e8-97ba-1cfd4f7a7075>" %}
Open a citation and inspect its source. Repeat this access check as the intended reader after permission changes; the clip does not show a permission change.
{% endembed %}

## Before you begin

Permission to review the source ACL and the relevant knowledge-base configuration.

## Key concepts

| Term               | Definition                                                                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Source permissions | Access rules for the original documents or records. Knowledge-base sharing does not necessarily grant access to every source.                           |
| Revocation         | Withdrawal of a credential or access grant. Check dependent applications and separately issued links when access changes.                               |
| Signed URL         | A temporary link authorizing access under its issuance conditions. It can expire and may remain usable until expiration after other permissions change. |
| Citation           | A reference linking a response to supporting source material. Preserve the source identifier and available location so readers can inspect evidence.    |

## Check access to a cited source

1. Change access through the authoritative provider or supported resource settings.
2. Check a new retrieval request under the affected user identity.
3. Check an existing citation separately, including whether it uses a temporary signed URL.

You know whether new retrieval and older links reflect the intended access change.

## Behavior and limitations

Previously issued signed URLs can remain usable until expiration. A new query applying access filters does not necessarily invalidate every link already stored in conversation history. Do not promise immediate revocation of all historical citations. Handle sensitive sharing through the supported source and link-access controls.

## Related resources

[File Inputs, Supported Formats, and Size Limits](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/file-inputs-supported-formats-and-size-limits.md)


---

# 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.stackai.com/technical-reference/files-knowledge-and-retrieval/citation-access-after-permission-changes.md?ask=<question>&goal=<user_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.
