Overview Access to U-M Box is determined by a person’s affiliation with U-M. As their affiliations change, so can their access to U-M Box. For example, students become alumni and faculty become retirees. This document explains what access people have in U-M Box depending on those affiliations and what steps to take if their affiliations change.
Use shared account folders for files that need be accessed/owned by a unit, team, group or department. Shared accounts provide unlimited collaborative storage. The data is owned by the shared account and remains in the shared folder, eliminating the need to transfer ownership between individuals when group members change. Offboarding is also made simpler as collaborators can be reassigned easily.
Overview Collaborate in U-M Box using MCommunity groups. Collaborations done using MCommunity groups will automatically update in U-M Box when the MCommunity group is updated.
All U-M Box accounts are required to use Single Sign On (SSO) with uniqname and UMICH password to login (as long as the app’s login allows it). If you previously set up an external password with your account, it will no longer work where SSO is supported. External passwords continue to be used for FTPS, WebDAV and third party (non-core) apps not able to use SSO. Enabling SSO does not end active Box sessions, but you will need to use your UMICH password the next time you log in. If you see a link to use SSO, do so.
View more CTools Project Site Migration information on our Training and Resources page.
This document provides information about managing the MCommunity Directory group profile associated with a shared account. Shared accounts allow a group to have a U-M Google or U-M Box account that is owned by that group rather than by an individual. This document includes information on changing the UMICH password used for that account.
Request a Shared Account Topics Overview Benefits Gmail Calendar Drive
Overview While both U-M Box and Google Drive are great for maintaining a shared document repository, ownership and permissions settings (including inheritance of these settings between top-level folders and their sub-folders) works very differently in each.