Best Practices Question - License Assignments per user per multiple assets

JosephWithCOR

Real world example. Adobe poshit software pick a package licensed per user, installable on two machines. (Multiple clients of mine work this way).

Is this the best way to enter this into ITFlow?

Because it is used across multiple clients I have a template - Name: Adobe / Version: Photoshop / Description: POS Desktop / Type: Desktop Application / License Type: User (so I can tie to a user) and Type: Device (so I can tie to an asset). Per client add license via template both user and device. Currently have to guess because the description is not part of the license template picker modal.

How can I tie that users license to those two assets? How about for nine users and eighteen assets?

wrongecho

I would say per user?

I think what actually happens is the user has to activate on each machine, and activating on machine 3 deactivates machine 1? Therefore you care and track the user licensed, not the machine?

JosephWithCOR

Thinking about it, if when creating the license / template you could specify 1 user 2 assets (adobe), or 1 user 5 assets (most microsoft office), or ?

But, then instead of having a single Adobe poshit pick a package I would have nine of them instead of one with nine users.

From clients \ Licenses you can tag either contacts or assets. But from either (contact or assets) you can only select matching (user or device).

JosephWithCOR

@wrongecho I have one named license used by two people, hence one login on two machines.