Hi,
we are planning to have multiple sites on a instance of Matrix.
We want to have some users (let's call them site admin) who will be able to create backend users for their own site branch.
The initial idea was to create site admin as backend user and give them Admin rights on whatever section of the asset tree they administer. Unfortunately, a backend user is not able to add a backend user… We don't want those users to be system admin, because they would have access to the other sites.
Any help greatly appreciated…
Bonus question: granting write/admin permission to users (not backend) or public doesn't do anything right?
Create an Asset Builder that creates Backend Users and only give permission to the site admins to access it.
Bonus answer: Incorrect. It gives them the ability to see Under Construction assets (though, not edit them, as the edit interfaces are locked).
Thanks for the bonus answer.
Thanks for the main answer as well, i don't dislike it particularly but… it feels a bit like another 'work around' to get things done. It is also adding an extra step for the site admin.
Why is a backend user not allowed to create another backend user?
Given that restrictions are assigned at the usergroup level, and that a backend user can be placed only in a usergroup if the creator has write access to it, I wouldn't think a backend could give more permission than they have to someone else.
I actually thought backend users could create other backend users. They certainly were not allowed when they were first built, but I thought Avi changed it.
The only thing I can think of at the moment is that a backend user who creates another will get write access to that account (standard asset creation rules apply). That could cause a problem while sys admins always have write access.
What, me change code? Never! 
I believe we discussed it, but I never made any changes.
Right. Thought that was one of your very first changes, being a simple 8 char change to the asset.xml file and all. Not exactly coding.