Bookmarks
Account
ACL
Tools
New
Other
ACL Add Role
Unless you plan on being a 'one man band' you'll eventually Add Users. You need to have a very clear plan for that User.
What should the User be able to do?Conversely, which Actions do you want to be excluded?
1) We have added a nonsense User to this slide show Account & now we'll add a Role for this User.We suggest that you do the same. Set up a bogus User first, (2) create an appropriate Role, and *then* (3) test the Role utilizing that bogus User as your login and retest thoroughly. Why?You may have misunderstood the functionality of an assigned Action - or - you may decide that a different combination is required. Start with very few Actions - and add as required.
Unless you plan on being a 'one man band' you'll eventually Add Users. You need to have a very clear plan for that User.
What should the User be able to do?Conversely, which Actions do you want to be excluded?
1) We have added a nonsense User to this slide show Account & now we'll add a Role for this User.We suggest that you do the same. Set up a bogus User first, (2) create an appropriate Role, and *then* (3) test the Role utilizing that bogus User as your login and retest thoroughly. Why?You may have misunderstood the functionality of an assigned Action - or - you may decide that a different combination is required. Start with very few Actions - and add as required.
This is a serious topic. If you find this 'boring' or worse - 'unimportant', then you should not be the Admin for your Account. It may be boring, but we cannot overemphasize the importance of the topic.
The subject it difficult and is rarely discussed within the context of an online Web Application or Database Builder. Roles and Privileges are nearly always Reserved for Administrators & Webmasters. Why?
-- The GUI is simple - but - the subject IS difficult and requires thought-- very few Web based Applications (to our knowledge) use a Schema based approach. By using a Schema, we can isolate your Account from everyone else's Account (Schema). If you make an error in judgement (create a bad Role), it has no effect on any other Account.
By using a Schema approach -- we have set up a system where you are (without all of the hardware, Apache, PostgreSQL, Php, ++ challenges) your own Webmaster.
Are you ready for this level of responsibility? If not, then choose someone else to be your Account Admin - and always have someone else that you trust, verify that your Roles work as expected.
We will test for you (on request) during your 2 week test period - for free.
The subject it difficult and is rarely discussed within the context of an online Web Application or Database Builder. Roles and Privileges are nearly always Reserved for Administrators & Webmasters. Why?
-- The GUI is simple - but - the subject IS difficult and requires thought-- very few Web based Applications (to our knowledge) use a Schema based approach. By using a Schema, we can isolate your Account from everyone else's Account (Schema). If you make an error in judgement (create a bad Role), it has no effect on any other Account.
By using a Schema approach -- we have set up a system where you are (without all of the hardware, Apache, PostgreSQL, Php, ++ challenges) your own Webmaster.
Are you ready for this level of responsibility? If not, then choose someone else to be your Account Admin - and always have someone else that you trust, verify that your Roles work as expected.
We will test for you (on request) during your 2 week test period - for free.
Name your Role (certain words are reserved), Describe your Role, then click Add.
The real work is found at 'Manage Roles' which is where you assign Privileges and Users to the Role.
The real work is found at 'Manage Roles' which is where you assign Privileges and Users to the Role.
Dev note: One reason why we chose PostgreSQL: Schema support.
TRUE online Workspace Collaboration is not possible without a solid understanding of Roles and Privileges.