it won’t prompt them to sign out if they’re signed into other computers with their NUL). Signing into an SDL app will not count against that person’s own named user license (NUL) activations (i.e. If you have to sign in to use the app, and the sign-in is a named person, how is SDL different from named-user licensing? so apps only activate from your organisation’s network). On top of this, you can also restrict IDs by domain and originating public IP address (e.g. You can restrict which kinds of ID are users allowed to sign in with via the Admin Console. They also state that users under the age of 13 cannot use personal Adobe IDs. You can’t use them otherwise, at all.Īdobe state that for schools (K-12 in the US and primary/secondary in the UK), only Enterprise or Federated IDs are supported. Yes, SDL apps only function when a user signs in with an Adobe ID, Enterprise ID or Federated ID. Here’s an FAQ-style breakdown…ĭo users have to sign in to use SDL apps?

Naturally, I spent much of my time mucking about with it, trying out all sorts of experiments to see what the results would be, or if something would break.

So yesterday, it showed up in my Admin Console. Shared Device Licensing (which I’ll refer to as SDL from now on) for Adobe Creative Cloud is here! If you want the skinny on it, go check out Mr Mule’s fantastic write up.

Ccda install helpx