Skip to main content
Question

Viewing a Report of Subscribed Users

  • August 1, 2022
  • 5 replies
  • 105 views

achess23
Novice III

Hello everyone,

We used subscriptions within Docebo where we assign licenses to groups of users and they get access to a number of catalogs.  I am trying to pull a report of a group of users to show their progress to stakeholders - but in the report I can only see those users who have enrolled into a course.  I want to see users who have a status of “Subscribed”. Is this possible? Am I overlooking something?

Thanks in advance!

 

5 replies

achess23
Novice III
  • Author
  • Novice III
  • September 9, 2022

Trying to bump this up and get some help - thanks in advance


Forum|alt.badge.img+1
  • Contributor I
  • March 12, 2024

@achess23 We have a similar need and we could not find a solution. I am considering to use the audit trail for this purpuse. 


  • Influencer I
  • June 11, 2025

Annarose.Peterson
Hero III
Forum|alt.badge.img+7

We use subscription licenses for catalogs too.  We make sure to put all of our “subscribed” users into a branch.  Then we can pull all active users in the branch (because they would all be “subscribed” to courses).  Then you can cross reference that to a report of all users who are enrolled into courses, which would give you a list of all who have access to our courses via a subscription and are not enrolled into anything. 

If you don't have your subscribed users in a specific branch or group, you could pull a list of them from the API: get    /learn/v1/sub_record/{record_id}/get_users


  • Influencer I
  • June 12, 2025

Hey, Annarose, thanks for the insights!

Using branches or groups is definitely a good idea. I would prefer groups though, for more flexibility; but still a separate method would be good to rule out any human mistake (one administrator could potentially forget to move one user in the related group/branch) or be useful for an administrator to double-check their subscribers.

We’re just exploring this functionality, since when we implemented “subscriptions” in our system, this functionality didn’t exist, so we found another way to manage “subscriptions”. And my plan was to explore the audit trail (as it was mentioned here in this thread) and the API, to find ways to extract the subscribers. So thanks for sharing that API endpoint, it saves time!