Determining Your Administrative Scheme

Determining Your Administrative Scheme

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.
    • Related Articles

    • Administering Concourse

      Administering Concourse as a whole is a huge step of any implementation process. For example, what level of access should a Dean have? Who will be able to configure integrations? Load courses in bulk? This article describes the two highest tiers of ...
    • Overview of Concourse Feeds

      This is a General Information article designed to give you a general overview of the Concourse feed process. If you are looking for technical specifications for feeds, consider exploring Construct and Process System Data Feeds or Automated Feed ...
    • Initial Group Permissions

      The ability to set initial group permissions allows system administrators to configure group permission settings before a syllabus is ever created in Concourse. Setting Initial group permissions will determine whether a particular group (e.g. ...
    • Domain Administrator vs. Course Manager

      Whether someone is a domain admin or a course manager is dependent upon the scope of courses for which you want the user to be responsible. In the case of a domain administrator, they will be able to operate on any course which falls within their ...
    • Course Templates Explained

      A course template typically refers to a syllabus that contains boilerplate language for everyone throughout an institution to adhere to. Such a document can go by many names (master syllabus, course outline, course format, etc.). Despite the ...