Enable groups instead of email addresses for the ackify-ce

[sejo]

When you want to self host, there is no option to do any team management or even use the groups in your upstream oauth solution.
This means for each document you send out one needs to fill in all the email addresses manually or use a CSV file.

This does not scale or is not really useable.

I am not asking this perse to be for free, but provide a self-hosting license model for these features maybe?

[Lord-ZuzurNC]

Hello,

I believe this feature would completely break the purpose of Ackify.

I also though about that but the purpose of Ackify is to personnally prove your reading. You can technically send a document to a generic mail but once 1 opened it, it will be confirmed and there is no way other can also do this.

Well that's my opinion.

Cheers.

[btouchard]

Thank you both for your comments.

@Lord-ZuzurNC Just to clarify: a group would only be used to compile the list of recipients. Each member would still receive their own link and confirm using their personal identity, so that individual proof would remain intact.

@sejo Resolving recipients from OIDC groups is not currently available, neither in the CE version nor in the hosted version. I’m willing to develop this feature, possibly under a self-hosted license as you suggest. Could you give me a rough estimate of the number of users you manage and which identity provider you use? That would help me determine if it’s worth the effort.
It would be great if other users could weigh in on their interest in this feature.

[Lord-ZuzurNC]

Ooh I completely misunderstood, Sejo was asking for group from the oAuth and not mail distibution. I'm sorry for the confusion.

Now that I understand, it would be great.

For now I use MagicLink as I'm currently testing the tool and making it approved by the HR for its usefulness. But I plan on using Gitlab connector (our local Gitlab is using LDAP, so that's an indirect LDAP connector) for roughly under 100 persons for our local branch (but maybe other branches of our company might show an interest and it can grow up to 200-ish personnes, but other branches are not in EU so they may not have these requirement).

[btouchard]

Nice !!! For your information, an existing SaaS version if you like : https://ackify.eu ;) Le lun. 28 sept. 2026 à 18:14, Lord_ZuzurNC ***@***.***> a écrit :

…

Ooh I completely misunderstood, Sejo was asking for group from the oAuth and not mail distibution. I'm sorry for the confusion. Now that I understand, it would be great. For now I use MagicLink as I'm currently testing the tool and making it approved by the HR for its usefulness. But I plan on using Gitlab connector (our local Gitlab is using LDAP, so that's an indirect LDAP connector) for roughly under 100 persons for our local branch (but maybe other branches of our company might show an interest and it can grow up to 200-ish personnes, but other branches are not in EU so they may not have these requirement). — Reply to this email directly, view it on GitHub <#29?email_source=notifications&email_token=ABGA4NHK45DJYBJUWBPBHVT5RKE4XA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWGQZTENZYUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18643278>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGA4NHBDTPR6QSMVCOKJTT5RKE4XAVCNFSNUABJKJSXA33TNF2G64TZHMYTANJUGI2DMNJSHA5UI2LTMN2XG43JN5XDWMJQGM4DSOJUGGQXMAQ> . You are receiving this because you commented.Message ID: ***@***.***>

[Lord-ZuzurNC]

If we have to go overboard with that tool I might propose the SaaS to make it accessible.

Thanks for the suggestion, I'll keep in mind.