Please, sir, may I have some more?
Permissions, permissions
Today we’re rolling out permissions at Scalr. You can now create users for everyone in your team and restrict that pesky intern’s privileges so he can’t log into servers and mess things up. You can even show off to a client that awesome architecture you built—with read-only access. Or partition your developers and system admins so they stop warring over the cubicles. Nerf guns hurt, you guys.
Here’s how to set up permissions: you add users, create their logins and passwords to access Scalr, and assign them to teams. Each team is associated with a specific environment. The team owner can then set permissions (through permission groups) to each team user individually, to allow Bob to terminate servers and Pat to launch new ones.
Create teams and users from the top menu
Just like you wouldn’t share your toothbrush with just anyone, you shouldn’t give full Scalr access to everyone in your organization. Starting with plans IPO and higher, you get to do just that. This allows you to maintain the sanctity of your toothbrush.
What’s next? We’re going to tweak and improve the UI while you play around with the new permissions feature. Remember, you’ll need to upgrade to the new plans (if you haven’t already) to use this feature.
Grant your users partial access to components
You can learn more by reading our thorough reference manual.