NetSuite consultancy question: best practices for ...
# general
r
NetSuite consultancy question: best practices for how to manage logins for clients who need ongoing support after an implementation? Ideally allowing multiple consultants to access the client's environment the easiest with minimal user seat usage ?
k
I generally discourage not using named logins unless specifically mandated by the client.
m
Multiple at once requires multiple logins.
We just use clientname@ourcompany.com as an email and the consultants share it.
Then scream at each other when they kick each other out 🙂
😂 1
k
Normally have an administrator inactivate/reactivate people as they need access
r
either of you tried using example+1@example.com where example@example.com is a shared outlook mailbox type deal?
m
Do you need to receive the emails?
Because that's not going to stop multiple people needing unique access seats
k
Which is why it's just easier to have named logins - and use the inactive checkbox to turn people on and off as they need it.
m
I think Kevins solution is the best, if the client has their own administrator and can tick and peoples access on or off as required
k
I do most of my ongoing support after go live as webexes when possible anyways so I can show them what they should learn anyways.
m
But if you're expecting to be the admin on their side then you'll need one 'permanent' login on their account and I'd say thats better to be a general email rather than a user in particular
c
i doubt they will but i asked a similar question at suiteworld when 2fa came out and they made a fuss about sharing logins for a consultancy being against their TOS... but its a necessary evil
m
I mean you can get a discounted user login for a NetSuite Partner licence
but it's only one licence.
k
My understanding is that you can get one discounted user login for partners
m
50% off afaik
k
just gotta ask the right way
r
good points ^ and thanks for all the input, the whole +1 thing I guess might be more of an idea for allowing the same outlook mailbox to first-time-auth user access to new env's for new clients
although I'm sure there would be security misgivings there even if it was workable as @creece was getting at
k
There are ways to do it securely - such as enforcing 2FA on the login
Takes a bit of work to do it that way though
c
ive seen multiple places use a login management tool like lastpass and then a singular google voice # that emails a distro list.
m
I mean if you're an admin 2fa is enforced anyway, we created a solution that sent the 2fa code to a phone number, which forwarded to a group email box so people could just get the codes without everyone having unique login
👍 1
Yeah that's what we did.
r
that's a good one, similar idea to what might help us out
right now we actually have a secure shared space with images of those QR codes our group can access