> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/records/achievements/search-edit-achievements.md). # Searching and Editing Achievements search options, including criteria and download search options, including criteria and download * by achievement title, status and/or tag, learner name, learner employer (and employer group status and region) and dates achievement was granted, revoked or expired * credentials.xls report - maybe need to get query language for this from Aleksey and move this to RCABC's queries, not sure it makes sense for other customers not using trades and employers outline: * shows information about the achievement template configuration, and about the user who was granted the achievement \[should we get rid of the CMDS refs outside of partition 3?] * authority \[what is this, or what is the plan for this, is it to do with blockchain maybe?] * shows information about the credential, when it was granted, expired, etc. edit options: * configure - set or edit a fixed or relative expiry date, add a necessity and a priority (contact support to configure a collection to use either of these fields) \[who uses these and what for?] * grant - change the granted date * revoke - revoke the credential and give a reason for the revocation \[who uses this and what for?] delete the achievement - if it was granted in error --- # 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.shiftiq.com/help/records/achievements/search-edit-achievements.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.