Introduction to Organizations and Sub-organizations

IN THIS ARTICLE
What are Organizations?
What is the point of Organizations?

What are Organizations?

In essence, Organizations (or Networks) are "homes" for Communities. Just like Communities, Organizations are owned and managed by individuals. And just as Community owners have the authority to invite users to their Community, promote Community members to Facilitator status, demote or kick out members, and set the rules for their Community, so Organization Administrators have the authority to invite users to their Organization, promote members to Administrator status, demote or kick out members, and set the rules for all Communities within their Organization.

Organizations are nested, which is to say that some Organizations have Sub-organizations. In general, we recommend that institutions build no more than two levels of Sub-organizations. This is to ensure that an institution's web of Organizations is tractable and manageable by Organization Administrators.

In general, an institution's Organization structure should mirror the institution's real-world internal structure. For universities, this structure is fairly straightforward. The majority of universities should institute a three-tiered Organization with the following hierarchical structure:

TIER 1: UNIVERSITY (e.g., Yellowdig University)

TIER 2: CONSTITUENT COLLEGE OR SCHOOL (e.g., School of Business)

TIER 3: ACADEMIC DEPARTMENT (e.g., Finance)

Ideally, your institution's Learning Technology Specialist (or a similarly equipped administrator) will serve as the Tier 1 Organization Administrator. Tier 2 Organization Administrators could include administrators of the school or college, or one and the same administrator could serve as both the Tier 1 and Tier 2 Organization Administrator. In general, department chairs or departmental administrators should serve as Tier 3 Organization Administrators.

What is the point of Organizations?

Organizations perform a wide variety of functions and are a hallmark of Yellowdig. For instance, Organizations...

1. Reduce the administrative burden on high-level Yellowdig admins. In a previous iteration of Yellowdig, all Communities (formerly "boards") occupied the same organizational tier. The result was a sprawling, unorganized mass of Communities—an especially acute problem for large universities with widespread usage. Because these Communities weren't partitioned by school or department, it was difficult to glean summary data without doing a deep dive. By categorizing Communities in an intuitive way, Yellowdig facilitates monitoring and administration.
2. Enable department- and college-level data analysis. To properly assess the efficacy of Yellowdig and the impact of different usage patterns, deans and administrators may want to know how specific departments are performing relative to the university and relative to the average Yellowdig Community. Partitioning Communities into department- and college-level Organizations allows Organization Administrators to produce fine-grained data visualizations.
3. Give department- and college-level administrators varying degrees of control over Community defaults. Especially in universities, one size often does not fit all. The needs of the Finance Department in the School of Business may be quite different from those of the Philosophy Department in the School of Arts and Sciences. Sub-organizations allow department and school administrators to customize default settings and rules without involving higher level administrators. This reduces the burden on high-level administrators and gives departments some freedom in managing their own curricula.
4. Facilitate and contain student-run Communities. Yellowdig isn't just for classes. It's a versatile student engagement platform that allows students to organize club meetings and reading groups, announce student-lead campus events, set up intramural sports leagues, and so on—all in a secure academic environment where students' personal data is protected. While we encourage students to create their own Communities, administrators often disable this feature for their entire institution. Administrators understandably worry about their ability to monitor "rogue" student-run Communities. But in Yellowdig, students can create Communities in a dedicated, tractable Tier 2 "Student Communities" Organization. These Communities are fully accessible by Tier 1 Organization Administrators, and students cannot hide the contents of these Communities. We strongly recommend that universities allow their students to create Communities within their dedicated Organization. Abuse is very rare, and the benefits of allowing students to create their own Communities are notable.

To this point, our discussion of Organizations has been relatively abstract. For a concrete example of how Organizations are implemented in universities, continue to the next article.

Audience: This help article is for Instructors, Designers, and Administrators. Students or Learners do not have access to these settings.