Umbrellas and how they differ from organizations

Umbrellas are the managing entities in each community. There may be one umbrella in a community or several. Each umbrella has the ability to setup custom processes for organization registration, event requests, budget management, and more. The ability to define your own processes is the primary benefit of having an umbrella and this is the reason why departments often create their own (versus sharing an umbrella with another department). Typically, members of the umbrella portal are only staff or faculty that help manage OrgSync on campus.portal_structure.pngThe umbrella is comprised of two parts: the dashboard & the portal. The dashboard provides statistics specific to the umbrella and access to tools that allow you to manage the users and organizations under the umbrella. You can access the umbrella dashboard if you select the Admin dropdown up top and choose your umbrella from the dropdown. 

The other half of the umbrella is the portal. "Portal" is a word used to describe the workspace each organization is provided in order to manage members, share content, and communicate with one another. An umbrella portal is very similar to an organization portal. The primary differences between an umbrella portal and an organization portal are 1) adding someone to the umbrella portal provides access to the umbrella dashboard (based on permissions) and 2) umbrellas have the ability to share content down to organization portals that they manage. 

To expand on umbrella sharing, if you create content in an umbrella portal you're provided a different set of visibility options (see screenshot below). If you make your content visible to organizations under your umbrella then the content will also be posted in their portals. The only exception is if you make the content visible to only members of the umbrella portal. This is the small number of staff that have been added to the umbrella portal who manage OrgSync on campus. 

Pro-tip: Avoid "hacking" organization portals. This term is used to describe campuses that share so much content to their organizations that it begins to take over their portals. For example, if you share 12 forms to your organization portals, they'll have 12 of your forms intermixed with their own forms that they've created. This makes the portal hard to use and it makes it seem to the org that it's no longer their space. This can lead to low student adoption rates. It's important to be picky when deciding what to share down to portals. If you want to create a form and make it visible to everyone, try creating the form in a portal under the umbrella. This allows you to create a form that can made visible to everyone but it won't display in other portals.

Have more questions? Submit a request

Comments

Powered by Zendesk