# Troubleshooting > Recover from missing access, stale reviews, interrupted saves, and incomplete previews without losing local work. **Experimental · private access. Public signup is not open.** Start with the project or Change link, the action you attempted, and the exact message shown. Keep unsaved local work and copies of any unsubmitted text while you investigate. Never include a password, API key, or session cookie in a report. ## I can sign in but cannot find the project Confirm the signed-in identity, then check whether it has a repository role. Signing in does not grant access to all repositories. Ask the owner or administrator to check the intended human role; the peer’s role is separate. ## The page changed while I was working Depot can refuse an action if the state no longer matches what the page showed. Copy any draft text, refresh, and inspect the current proposal or custody state. Check whether the action already succeeded before submitting another one. For an interrupted save in Space, use **Retry saved operation** when offered. **Inspect outcome** shows recorded steps and current facts after a stale result. See [Space recovery](/docs/space/depot/#recover-an-interrupted-operation). ## My approval is visible, but the Change still needs review Check the review state and source revision. Published source changes make old approvals stale. A later decisive review can replace an earlier decision, and loss of the reviewer’s permission can stop it counting. A comment is not an approval. Read the latest proposal before approving again. If the source is current but merge is blocked, inspect the approval requirement, merge status, and caller permissions. Ask Kin to explain and resolve conflicts. The merge operation checks both branches again even after the page showed ready. ## I cannot see a comment, review, or merge button Read access allows inspection. Contributing a comment needs write permission; review and merge need maintainer authority. Installation admin status alone does not grant those repository roles. A finished Change or unavailable diff can also limit controls. See [People and permissions](/docs/depot/access/). ## My saved files are not in Code Check whether they were only saved locally, published to a proposal branch, or merged into the shared branch. Open the Change or select the relevant branch. Ask Kin to report the exact saved location before attempting another save or overwriting local files. ## A file or Change preview is incomplete For a large Change, inspect individual files or folders and their before/after versions. For a file, try **Download file**. Files above the browser’s 8 MiB raw limit need a repository bundle or authenticated Git access through your peer. Do not treat the visible portion as the whole file or approve unseen work. ## The peer lost access If access was ended, stop asking the peer to retry the same operation. Sign in with your human identity to inspect **Custody** and download history if needed. Restoring the peer’s repository role requires a separate authorized grant. Suspension and a missing repository role are different facts; read the page’s explanation. ## I requested deletion, but the repository remains That is the current retention contract. The request is recorded, while files and backups remain until confirmation and operator removal. It does not notify an operator automatically. Contact the person responsible for the installation and confirm the intended scope. See [Request deletion](/docs/depot/custody/#request-deletion). ## A sign-in attempt expired or a service is unavailable Start again from the original Depot link. If the problem persists, keep the time and non-secret error message for the installation contact. A connection failure does not by itself say whether the last save completed. Preserve local files and inspect the saved result when access returns. _Source authority: Kinra Site (src/content/docs/depot/troubleshooting.md)._