First it is helpful to understand how permissions are allocated and enforced at various levels throughout the system. We highly recommend you read our article,
Administering Concourse, to get a robust walkthrough of our administrative permissions. From there you can start to figure out how your organizational structure and the goals of your syllabus project equate to the people who will be involved.
At the highest level you will have a handful of system administrators. These are the people who will have access to every element of the system and can grant similar authority to other users. Typical titles for these people will include high level academic and technology administrators, such as Provost's, Dean's, CIO's, and technology directors. In general these will also be the only members of the project team that should directly interface with Intellidemia.
The next set of administrators will usually be a set of folks with access over a particular element of the system, such as template management, integration, auditing, and reporting. In most cases these will also include some of the folks above, but then add Department Chairs, Administrative Assistants, Institutional Researchers, and Database Administrators. Many of these users will be granted access through the use of domain permissions.
Beyond these administrators comes instructors and students. Here users will actually be enrolled in course groups to give them rights to edit and/or view syllabus content. Public and guest access would also fall into this category, though they are a special case as they are technically not enrolled in the course but rather receive a default view based on the permissions provided to them.
As you work through your Concourse deployment, it may be a healthy exercise to map out the various system permissions against user roles (and in some cases names) much like an organizational chart.