> ## Documentation Index > Fetch the complete documentation index at: https://thehyperstack.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Change Requests > Recipients ask you to fix a mistake on their credential. You approve or reject it in one click. A typo in a name happens. With **change requests**, the recipient tells you what is wrong, and you fix it in one click. No emails back and forth, and no new credential to issue. Every organization has change requests. There is nothing to switch on. ## How it works **1. The recipient asks** From their wallet, the recipient types the correct name or detail and adds a note if they want. **2. You review** The request shows in your Studio under **Credentials → Change requests**. You see the old value, the new value and their note. **3. You approve or reject** Approve, and the credential is updated at once. Reject, and nothing changes. Either way, we email the recipient your answer. ## What recipients can ask to change * Their **name**, as it shows on the credential. * Any of your [custom attributes](https://thehyperstack.com/docs/tutorials/advanced-setup/custom-attributes.md), for example a grade or course hours. To change anything else, such as the email, the group or the dates, the recipient contacts you and you [edit the credential](https://thehyperstack.com/docs/tutorials/credential-setup/managing-credentials.md#edit-a-credential) yourself. ## For issuers: answer a request ### See new requests A number next to **Credentials** in the sidebar shows how many requests are waiting. Go to **Credentials → Change requests**. ![The Change requests tab with four open requests, each showing the old value struck through and the new value](https://mintcdn.com/hyperstack/PUoRDMgjwa959UZV/images/change-requests-list.webp?fit=max\&auto=format\&n=PUoRDMgjwa959UZV\&q=85\&s=c16acab5e40da2f0959cb50cc0251f20) Open requests are listed oldest first, so you can answer them in order. Each row shows: * **Recipient**: the name and email of the person who asked. * **Credential**: the group code and the credential ID. Click the ID to open the credential. * **Change**: what they want to change, with the old value struck through and the new value next to it. * **Asked**: when they asked. ### Approve or reject **1. Click Review on the request** **2. Check the change and the note** If someone on your team changed the value after the recipient asked, a yellow notice tells you. **3. Add a reply (optional)** We add your reply to the email we send to the recipient. **4. Click Approve or Reject** ![The Review change request dialog with the name change, the recipient's note, a reply and the Approve and Reject buttons](https://mintcdn.com/hyperstack/PUoRDMgjwa959UZV/images/change-request-review.webp?fit=max\&auto=format\&n=PUoRDMgjwa959UZV\&q=85\&s=06e4c9981bf39f740158601a0f7d4355) When you approve: * The credential page, the downloads and the verification page show the new value at once. * The credential **link stays the same**, so links the recipient already shared keep working. * The change is saved in the credential's history and in your [audit logs](https://thehyperstack.com/docs/tutorials/advanced-setup/audit-logs.md), the same as an edit you make yourself. > [!NOTE] > > Each request is for one detail. When a recipient asks for two changes, for example the name and the course hours, you see two requests. Approve or reject each one. ### Requests on a credential's page When you open a credential that has open requests, a **Change requested** card shows at the top. Click **Review** to answer from there. ![A credential page with the Change requested card listing a name change and a course hours change](https://mintcdn.com/hyperstack/PUoRDMgjwa959UZV/images/change-request-credential.webp?fit=max\&auto=format\&n=PUoRDMgjwa959UZV\&q=85\&s=b5e1b0bb8afb85bdfcb96c283e60273d) ### Answered requests Click **Answered** to see the requests you approved or rejected, who answered them and when. Requests the recipient cancelled show as **Taken back**. ![The Answered view with one rejected and one approved request](https://mintcdn.com/hyperstack/PUoRDMgjwa959UZV/images/change-requests-answered.webp?fit=max\&auto=format\&n=PUoRDMgjwa959UZV\&q=85\&s=cece485d276813418d770e2aff1a84ff) > [!TIP] > > Only team members with the **Admin** or **Issuer** role can see and answer change requests. See [Team management](https://thehyperstack.com/docs/tutorials/advanced-setup/team-management.md). ## For recipients: ask for a change You can send this part to your recipients. **1. Sign in to your wallet** Go to [hyperstack.id](https://hyperstack.id) and sign in with the email your credential was sent to. **2. Open the menu on the credential** Click the **⋯** button on the credential, then **Request a change**. ![A wallet credential's menu with Open credential, Request a change and Make private](https://mintcdn.com/hyperstack/bkK6_JVKeMlxGhkQ/images/wallet-request-change-menu.webp?fit=max\&auto=format\&n=bkK6_JVKeMlxGhkQ\&q=85\&s=a241888dc86bbc6594b148fd1fdfdc04) **3. Type the correct details** Change only what is wrong. Add a note to explain, if you like. Then click **Send request**. ![The Request a change dialog with the name changed and a note](https://mintcdn.com/hyperstack/bkK6_JVKeMlxGhkQ/images/wallet-request-change.webp?fit=max\&auto=format\&n=bkK6_JVKeMlxGhkQ\&q=85\&s=dfe16dd53a619a232d965b0c36187e6c) **4. Wait for the answer** The credential shows **Change requested** until the issuer answers. We email you when they do. You can also click **Request a change** under the credential on its own page, when you are signed in. Changed your mind? Open the menu on the credential and click **Cancel change request**. ## Questions > [accordion] Does it cost credits? > > No. Approving a change request uses no credits. > [accordion] Do we get an email when a recipient asks? > > No. New requests show as a number next to **Credentials** in the sidebar and on the **Change requests** tab. > [accordion] Does the credential stay verified after a change? > > Yes. The credential keeps its link and stays valid. Verification shows the new details. > [accordion] Can a recipient ask again after a rejection? > > Yes. They can send a new request from their wallet at any time. They can't send a second request for the same detail while the first one is still open. > [accordion] Can recipients ask for a change on a revoked credential? > > No. Change requests are only for published credentials that are not revoked. > [accordion] Can I turn change requests off? > > No. Every organization has them. Nothing on a credential changes until you approve it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.