Forum Discussion

ppatel's avatar
ppatel
New Contributor
2 years ago

Named User Vs Generic

Out of curiosity, are there any folks out there that have opted to have some "Generic" users/licenses versus specific named users in their environments? A couple of places where I think a generic wou...
Security
  • MikeG's avatar
    MikeG
    2 years ago

    Hi ppatel , It's also best practice to not have Task Scheduler run with a contractor or employee ID.  i.e. an implementation partner configuring automated tasks should use a generic ID like OS_Automation or SVC_OneStream (when setting up Task Scheduler tasks) as a Native account that will never be disabled.  I see that a lot.  Jobs setup on the Task Scheduler with a named individual that is only there for the implementation and not a permanent, long term individual working in the app.

    For auditors, I'd err on the side of not letting them "in", just extract out what they think they need and hand it over in a PDF or Excel file.  Creating temporary accounts for auditors may not align with a customers security policy.

    Hope that helps, interested in others experience and potential use cases for generic ID usage.

     

MikeG's avatar
MikeG
Contributor III

Hi ppatel , It's also best practice to not have Task Scheduler run with a contractor or employee ID.  i.e. an implementation partner configuring automated tasks should use a generic ID like OS_Automation or SVC_OneStream (when setting up Task Scheduler tasks) as a Native account that will never be disabled.  I see that a lot.  Jobs setup on the Task Scheduler with a named individual that is only there for the implementation and not a permanent, long term individual working in the app.

For auditors, I'd err on the side of not letting them "in", just extract out what they think they need and hand it over in a PDF or Excel file.  Creating temporary accounts for auditors may not align with a customers security policy.

Hope that helps, interested in others experience and potential use cases for generic ID usage.

 

NicoleBruno's avatar
NicoleBruno
Valued Contributor
2 years ago

Exactly as Mike mentioned, we have a "TaskScheduler" native ID which is the only non-specific user set up in our app. We also don't provide access to our auditors. Requests go through the admin, aka me 🙂