In a national organization, as with our example, that has local, neighborhood, or state entities, you can enable a dues-paying member to join a specific region. Drupal handles the assignment of user roles and permissions very straightforwardly, in a large "grid" of user permissions similar to the above. The specificity of the roles, and the permissions associated with those roles, make it easier for the organization to divide up functional requirements. Likewise, it may not be required for the Directory Manager to process payment-related requests. For example, it may not be necessary for the Treasurer to handle individual directory listings.
With the ability to manage the roles and the permissions available to users, it becomes easier to control the flow of information by allowing only managers with the "need-to-know" access the details relevant to them. Both of those managers may report to a Treasurer role, a person who prepares monthly reports on income, new and existing members, or new and current sponsorships.
Doing this simplifies the implementation of editorial controls or permission management details.įor example, a Dues Manager role may be assigned to a user who only reviews new orders and existing orders around dues-paying individual members. The Dues Manager requirements and access may differ from the Sponsor Manager role, which allows that designated user to review new and existing sponsorships. However, local branches may also spin up subsites to allow for different levels of users to access only the content that is relevant to them. Users may log in and register to a centralized instance of Drupal, e.g., the main office. We'll call our organization "International Guild for Drupal Project Managers," which we will say is a dues-paying member organization with offices on K Street right near the White House. Note that this concept applies across many different organizational models, but we're using this one to illustrate some of the details. The example: National HQ with regional chaptersĪ typical scenario in Washington DC is one where a central organization serves as a "National Headquarters" or "Global HQ " however, branches at the state-wide, regional, local, or neighborhood level may have their own operations and leadership, yet act as "chapters" for implementing the central program.
This article focuses on a specific example-a nationwide parent organization with many local, regional chapters-to illustrate how this works. Independent groups coordinated around a central structure may find a good fit with Drupal's access management system. And, umbrella government organizations encompass many related but independent programs and agencies, as is the case with Digital Services Georgia. In higher education, universities like New York University have many departments. For example, large enterprise companies, such as IBM, have many business units. Drupal's versatile permission system, applied at scale, makes Drupal an excellent platform for managing large organizations with multiple subsidiary groups, each of which has particular needs and requires a unique web presence.
0 kommentar(er)
