Creating Accounts and Containers on Community
Community is provided to meet the collaborative working and social needs of the campus community and campus-sponsored external communities. The server utilizes Moodle in order to provide options for public or private information dissemination and offers a wide array of collaboration activities. Unlike the academic instruction-based server “Cougar Courses,” Community is not rolled every academic year or archived by semesters. Community assumes on-going activity throughout the year or over multiple years.
Community is available upon request by users with a valid campus account/username, but may include participants from the external community as long as containers are maintained/sponsored by one of these valid campus account holders.
Community members may request a new website container from the "Request Container (login first)" menu at the top of the site. The server administrators will receive these requests and approve or deny requests, based on compliance with the server’s availability guidelines and purpose.
CSUSM Users --
- If you already have an account with CSUSM (i.e. an email account like firstname.lastname@example.org) then you do not need to create an account on Community. In many cases, your account will have already been added. If not, the easiest way to get your account into the system is to just try logging in with your username (ex: doe001) and authenticating with your campus email password. The system will generate a basic account with your Name and email and from there you can use the site or further edit your profile.
- If you are trying to add other CSUSM users to your container and cannot find their name/account, you can either have them try logging in first (see previous bullet) or contact email@example.com in cases where large numbers of accounts are needed (batch uploading of users).
Non-CSUSM Users --
- Community allows for external accounts to be created via an email confirmation system. Use the "Create and account" option located in the Login block on the left to get started. From there, you can enter your desired username to use for future logins, a password to go with that, and then enter your valid email address that will be used to confirm/complete the process. Submitting the form may allow you into the system temporarily, but it is important to check your email for the confirmation link and complete that process.
- Remember that this process just gets your account into the system and does not add you into any containers. The owners of those containers will usually add people directly by searching for the individuals name or email address, so make sure those fields represent your real name to make it easier for them. In some cases, containers allow for a self-enrol option and that can be completed once you have created and confirmed your account.
An attempt to offer more multi-purpose roles than typically found in academic settings was applied to the following list of available choices on Community
Owner >> Coordinator >> Designer >> Participant >> Reviewer >> Guest (not assigned, used by any unauthenticated visitor)
- "Owner" | Owners can do anything within a container, including changing the activities and grading participants. They can add people into any lower role. Typically, there is only one owner per container because this is the primary contact in case of administration notification.
- "Coordinator" | Coordinators can do anything within a container, including changing the activities and grading participants. Coordinators essentially have the same abilities that container owners have, except the ability to assign other coordinators to the container. They can add people into any lower role.
- "Designer" | Designers can do anything within a container, except grading participants or viewing participant submissions for individualized activities -- like assignments or quizzes. The designer role is mainly for individuals responsible for creating structure or design for the container.
- "Participant" | Participants generally have fewer privileges within a container.
- "Reviewer" | Reviewers have few privileges within a container besides read-only access. This is like a guest role, but it requires the user to be logged in and known within the container.