Feature Requests

Ideally, team member permissions could be locked down to the individual Group Settings (Skills, Description, Earning Criteria). Larger organizations would like to ensure governance/standardization is consistent across departments and would like the ability to lock down certain group parameters as listed above.

A customer building out a new credential strategy would like to display/tag a high-level classification label (e.g. "Certification," "Advanced," "Foundational") on the credential page. They're structuring their program into four tiers: Tier 1: Certification (Certified) Tier 2: Skills (Demonstrated) Tier 3: Knowledge (Trained) Tier 4: Engagement They'd like each issued credential to visibly display its tier, ideally as a styled label near the top of the credential page (not buried in the skills section or a custom attribute list further down). Today, Skills Frameworks and Custom Attributes don't cover this use case since they're skill-level or attribute-list based rather than a prominent type/tier tag. A configurable "credential type" or "level" label that issuers can define and apply per group, and that renders prominently on the credential page, would help programs like this align their badge structure with recognized industry patterns. They also mentioned wanting this to be a searchable option in the Spotlight Directory as well.

PUCRS would like to have a toggle for team members to be able/unable to export.

Several clients extend the expiration date through API to show longevity of the credentialee. There is currently no way to send a "renewal" email. I was hoping since our system knows to charge a credit there must be some sort of trigger we could create so that when a credential is renewed via an extension of the expiration date an email could be sent to the recipient notifying them of the credentials renewal. This is also common for clients who allow their recipients to renew early.

Context: The revoked credential status feature has already been scoped. This work may offer a customers a way to highlight that a credential has been revoked without deleting it. However, some customers may want this status internally displayed but not externally. The need: For some certifications (such as IT/technical certifications) tied to cheating or exam fraud cases, organizations may need revoked credentials to never be publicly visible, not even with a "revoked" label attached. The concern isn't hiding the fact that a credential was revoked internally, it's avoiding public shaming of the individual, which can cross into a privacy violation for cases where the underlying issue was personal misconduct rather than a public safety concern. This is different from fields like medical or safety certifications, where an organization might want a public "revoked" label to stay visible for verification purposes. The need varies by industry and use case. Suggested consideration: Allow visibility of the revoked status to be configurable at the org, group, or collection level, so customers can choose between: Publicly visible "revoked" label Non-public revoked status, returning something like a 404 to unauthenticated public viewers, with the status still visible to the signed-in credential holder and retained internally for org records Why it matters: Without this option, some customers may be pushed back toward full credential deletion to avoid public exposure, which loses the internal record-keeping benefit the revoked status feature is meant to solve for.

Board of Certification for the Athletic Trainer is wanting the final certificate of a pathway to have the option of being manually issued vs automatically issued when required nodes are all complete. They issue credentials for courses, but in order for a recipient to earn the Program Certification, the recipient needs to submit other items that aren't going to get badges. The issuer tracks these completions internally (submitting necessary paperwork, video completion, etc). They want to be able to issue the final certificate manually after all pieces of their process are completed.

It would be nice to be able to customize the date format and choose to show the 4 digits year only on credential designs through a (<date>, <format>) function for attributes.

A client is requesting the ability to create and update groups via a spreadsheet upload, similar to how credentials can be created via spreadsheet for recipients. Currently, this can be done manually in ACMS, but you can only create one group at a time. Similarly, you can create groups via API, but not all have the technical resources to complete this. It would be helpful if clients could bulk create groups via spreadsheet, using all of the fields that are needed for a group creation via API (group name, identifier, description, link, design ID, etc). Similarly, this would be helpful to update groups, especially when we have new feature releases, so client can easily go back and update the new fields in their groups.

JHU has requested the text for Issued On and Expired On not be in all CAPS on recipient credential pages for accessibility reasons.

Daniela's School would like to receive emails when they are close to running out of credits. They recently ran out of credits but were not aware, so credentials stopped being issued through their integration.