Sandboxing users

Hey Matt,

Is there any way to sandbox users such that they have restricted access to my wyDay account?

Not currently. Of course you can restrict users to specific broad actions, but there isn't the fine level of control you're looking for (restricting to specific product keys). The best way to do this now is to use the web API and give the reseller access through that.

This sounds like an interesting idea. I can see the benefit to some of our customers. I have some ideas on how something like this might work, but I'd like to hear how you'd imagine it works. That is, explain the ideal versions of something like this.

Hi Wyatt,Thanks for the reply.I haven't had a lot of time to think about it, but off the top of my head:

1. The ability to let certain users create keys, but not see or modify any other keys. Ideally, the keys that this user creates would be flagged in such a way that this user could see and manage them. This would solve one issue I have now with a reseller - yes, I can create keys in advance, but so much easier if the reseller makes them as he needs them. This helps the audit trail - number created, when created etc - and also means that information such as email address etc can be entered correctly at the time. Otherwise I just create a bunch of keys with generic identifiers, have to rely on a report from the reseller on number sold etc etc.As a further part of 1. it would be nice to restrict to certain products/feature sets etc. and perhaps even limit the number of keys that can be made, without further authorisation from me.

2. Not dissimilar to 1, it would be nice if I could again flag a set of keys that belong to a user, so that this user can go in and modify key features. This would fix the upgrading-through-a wholesaler issue that we have discussed on another thread. I could assign all the previous sales of this guy to him, and he could log in and make the change himself when he sells the upgrade.

For me, both of those functions would be great. Of course, I could do them somehow with scripts online, but easier and more secure if it were within wyDay.

cheers,Matt

These are good ideas and I can see how they can be broadly useful to many of our customers. We'll start chipping away at these problems. Unfortunately it won't be quick work because it requires a major restructuring of how our database is setup along with major code changes.

But this is useful and we will work on it.