Some terminology that will be helpful:
Term
Meaning
Organization
Any company, group, team, committee, association, department, competition that logically groups a set of people together is given the generic term 'organization' in pagebloom. Organizations can be structured hierarchically so that a top level organization (eg. company or sports club) may have sub organizations (eg., departments, committees, competitions) and those sub organizations can have futher sub organizations to any required depth (eg., client support team, sporting team).
The pagebloom administration screens have a 'Structure' menu under the Organization menu item that allows quick navigation both up and down your organizational structure.
User
A user is a person who has an account in pagebloom. A user can have one or more roles in a given organization.
To see the users that have been granted roles within an organization go to Organization > People menu in the pagebloom administration pages.
Role
A role that can be assigned (or revoked) from a user. Users are given permissions to perform certain operations based on the set of roles that they have been assigned to them.
Roles are inherited - this means that if a user is granted a role in Organization A then that user will inherit that role in all sub organizations of Organization A.
To grant or terminate a role for a particular users go the 'People' section under 'Organization' in the administration menu
For example:
Sports club scenario: if a user is given 'ArticleApprover' role in the top level 'Sports club' organization then he can approve articles for all teams. If instead he was given 'ArticleApprover' role for the 'Under 9- Under 19' then he would only be able to approve articles generated for teams under that group.
Task
Tasks can be generated both manually and automatically. Assignment of a task to a user is based on the roles that users have.
When a new task is created in the system an email is sent to the users who have a role that enables them to process that task. If a user is no longer responsible for processing a particular type of task then the role corresponding to that task should be terminated.
To give a user permissions on your site:
Pagebloom allows for website operators to interact with people without forcing them to establish their own account. i.e. without forcing them to click the 'Sign up' button and create a user account.
This is what is indicated by the 'No user account' value seen in the 'User state' column of the 'People' administration panel.
So they effectively are a 'Person' that is known to a particular pagebloom organization but they do not have their own 'User account' and therefore will not be able to "Sign in" to the system and perform 'user level' operations.
If a user requires user level access such as, to perform administration operations, then they must be able to be authenticated by the system via the Sign in form and for that they need to establish a user account by signing up using the same email address that they are already associated with in the system.
To create a user account go to "Sign in/Sign up" and then click on the "Sign up" button and enter the details on that form, including which password is to be used to authenticate the user each time they sign in.
That will establish a user account for the person and then you should see the "No user account" replaced by "Active" for that person in the 'People' administration screen.
Pagebloom uses a role-based permission system to control access to restricted features of your website. For example, only people with the Author role can create news articles. These roles apply to the organization they're configured for and are inherited by the user assigned to them in all child organizations of the organization they are configured in.
If you want to grant a role to a person who has never had a role in your organization you first need to add them. See the previous question for details of how to add a new person/user to your organization.
You can add or remove roles for users you've already set up.