I'm interested to see how others are approaching temporary users, eg interns or work experience users and licensing? Do you create a new account for each intern or use shared / generic accounts for them?

Question

Answer

Each of our interns, contractors and the like gets an individual, nominative account (AD account, Okta account, Google Workspace account). Shared / generic accounts are forbidden. As far as I know we just ensure that we have enough licenses of each of those solutions to cover the peak usage during the year, and reassign licenses from one temp to another as they come and go over the course of a year.

Answer

Individual accounts, never shared accounts.

Answer

Never shared opens too much risk.

Answer

We create group base even in AD and then create account assign to group base permissions or profile base

Answer

Treat them like regular users and buy SaaS that allows for flexible licensing and limited permissions. If you are buying inflexible SaaS you are probably doing it wrong. If you are not buying SaaS you are almost definitely doing it wrong. Slack’s licensing model is the perfect one for others to follow.

Answer

Always new accounts. Whilst yes a cost and time implication, audit and tracking in the case of an event of someone doing something stupid is always calming

Answer

We create accounts for each intern. Those accounts are then deleted at the end of employment. We only license a few things for all employees. Most licenses are allocated on a &#34;Must Have&#34; basis. If you don't need it, you don't get it. One thing we do is if a particular software has a free &#34;Viewer&#34;, a software package that allows you to view but not change the saved file from some expensive software, we will install that. We find that many people want software &#34;X&#34;, but they don't actually create with &#34;X&#34; they just review or read the content and don't need the expensive creation software &#34;X&#34;. A viewer application works just fine.

Answer

Always a unique account for purposes of non-repudiation among other things.

Answer

Each user needs their own account - no shared accounts. Also can mark as intern so others know e.g. Jim.smith.intern the same same you should be marking contractors e.g. jim.smith.ctr

I'm interested to see how others are approaching temporary users, eg interns or work experience users and licensing? Do you create a new account for each intern or use shared / generic accounts for them?

Content you might like

Do you plan to deploy security containers in the next 6-12 months?

What’s the best place to start when evolving data governance?

What technology solution are you using for your employee experience platform? How does it integrate with your HCM solution and intranet solution? Any do's and don'ts, lessons learned to share?

What are some great on-prem and SaaS programs for internal PKI and Certificate Life Cycle Management?

How does your company handle AD accounts after a person leaves the company? We have been changing the passwords, disabling them, and moving them to a separate OU, but I'm interested to hear if you do anything else.