Feature Requests

In order to do proper automations, the API needs to be expanded. To the very least, the following should be available: Create Event (or at least Duplicate - structure, no data) Assign Certificate Template to Category (Canva as a source?)* Add Recipient (especially in bulk) Send Emails * If there was a way to extract/send a Canva design into a design export format then Assign Certificate Template would be rather straightforward.

Pathways are a very interesting feature. In order to be fully usable, we recommend the following improvements: Better responsive UI > Pathways should be easy to embed into iframes or other websites Improve the cookies > Every time the page is loaded the cookies toast comes out, making it really unpleasant Allow Pathways to be seen from the users' wallet > You want to showcase people the kind of pathways you are currently undertaking Consider Pathways to be built around several Categories of several Events > It makes little sense that an Event is tied to a date and expect that all stages of a Pathway are accomplished in that only date. It's more likely that it's a progression across at least several weeks Each Category should be given its own URL so that "Earn" buttons take you directly to the actual course/event where the stage can be earned Badges associated with a Category should also be reflected in the Pathway Allow Pathways to have some basic branding (baseline color + icon at least + Tags + Font? > Because if you embed you want visual consistency) Pathways may need non-linear progression > Allow the possibility have a Category to branch out into a different "line" and to branch back several lines when necessary. Allow existing Recipients in a Category to be copied to another Category in bulk so they don't need to be recreated again. (This is going to be very handy as a Recipient moves from one stage to another through their pathway.) I am happy to split all of these into separate tickets. There's more to be looked into when it comes to Pathways and Company Page.

It would be nice to have your own bank of templates, to duplicate on different events and categories. Right now we need to export and import the template.

Please integrate with MasterStudy LMS to send certificates on course completion.

N8N is a powerful integration platform, similar to Make.com , but with significantly more advanced and robust capabilities.

مبروك النجاح

Problem: On occasions, certificates need to be signed by more than one person/institution. When these are not related to you, storing their digital signature may raise concerns and, depending on the applicable regulations, may be legally problematic. Request: Make it possible for "external" signatures to be added to a template. Example of how could it work: Template is designed, 3rd party signature component is placed on it. The component requires an email. Somewhere in UI a method to send an invite to that email is available. Upon activating it, the 3rd party receives an invitation to upload their signature. The signature is stored TEMPORARILY and indicated as Ready in the template. When the certificates are generated, all involved signatures are embedded. When all certificates are done, the 3rd party signature is deleted and a notification is sent to the 3rd party.

Currently, the custom smtp settings are saved in the user account. For company accounts this is not scalable and represent a security risk because we may want to use the same settings across the account and we don't want to be sharing smtp login credentials with all users. Also, updating the account password used in the smtp settings in all user accounts when it's going to expire will represent extra burden for IT.

Problem: The way the events are currently organized is a simple list. As that list grows so does its management complexity. Request: Allow for 2 methods of organizing the Events. 1) Folders > This is part of another request so we upvoted it there. 2) Calendar View > Simple calendar where we could see when an Event has been done so we can navigate across years & months. Priority: 1 then 2 (because a folder organization would allow to organize the Events in their corresponding Year/Month/Event path.)