Managing permissions in a collaborative workspace

[0001] A collaborative workspace (henceforth “workspace”) refers to functionality that allows individuals to work on a shared task in a coordinated fashion. A typical workspace defines permissions which identify a collection of members who are permitted to interact with the workspace. The permissions also define the manner in which the respective members are permitted to interact with the workspace. The workspace also commonly defines a collection of items (e.g., document items, data items, etc.) associated with the workspace. In operation, authorized members may engage the workspace (in a manner defined by the permissions) to work on the shared items in a coordinated fashion.

[0002] In one approach, a user may create permissions by accessing a separate administrative user interface presentation outside the context of the collaborative workspace. The separate administrative user interface presentation may present a flat list of individuals. The user can scan this list and pick out, one user at a time, individuals who shall be granted access to a workspace (thus becoming members of the workspace). The user may also assign permissions to the selected individuals using this administrative user interface presentation.

[0003] The above approach has potential shortcomings. For instance, the user may find it a burdensome and disruptive task to access and interact with the separate administrative user interface presentation. For instance, the user may find it difficult to scan a long list of individuals. Further, since the list is flat, the user may find it difficult to quickly discern the permissions assigned to various individuals in the list. Further still, the user may find that the list does not encompass the complete universe of individuals with which the user may wish to interact. To remedy this issue, the user may decide to access yet other types of systems (having their own unique user interface presentations and protocols for managing individuals). These additional operations may increase the complexity of creating and managing permissions. The above-described approach may have yet further shortcomings.

[0004] The above potential drawbacks may discourage a user from defining robust permissions for a workspace. For instance, the user may decide to assign permissions to members in a relatively broad-brush and general fashion. This tactic, however, may compromise the security of the resultant workspace.

[0005] An approach is described for managing permissions in a collaborative workspace. According to one illustrative implementation, the approach entails providing a workspace user interface presentation to a user through which the user may interact with the collaborative workspace. In response to the user's instruction, the approach presents a permissions user interface presentation to the user without losing a context associated with the workspace user interface presentation.

[0006] According to another illustrative feature, the permissions interface presentation visually organizes a set of workspace members into groups corresponding to two or more permission level categories. The two or more permission level categories are associated with different respective levels of access to the collaborative workspace.

[0007] According to another illustrative feature, the approach allows the user to change a permission level of at a workspace member from an original permission level category to a target permission level category. In one implementation, this operation involves performing a drag-and-drop operation to graphically move the workspace member from the original permission level category to the target permission level category. The user may also activate additional information regarding a workspace member and change the permission level of this member by acting on the additional information.

[0008] According to another illustrative feature, the approach allows the user to add a new member to the existing set of workspace members. The new member may be associated with a local system or an alternative system. In the former case, the approach displays a list of local system persons who are associated with the user. The user can select one or more these local system persons as new members of the collaborative workspace. In the latter case, the approach allows the user to select the alternative system from which new members will be selected. In response, the approach displays a list of alternative system persons who are associated with the user. The user can select one or more of these alternative system persons, changing their status to local system persons. At this time, the user can select one or more of the local system persons as new members of the collaborative workspace in the manner described above.

[0009] This Summary is provided to introduce a selection of concepts in a simplified form; these concepts are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0023] The same numbers are used throughout the disclosure and figures to reference like components and features. Series 100 numbers refer to features originally found in FIG. 1, series 200 numbers refer to features originally found in FIG. 2, series 300 numbers refer to features originally found in FIG. 3, and so on.

[0024] This disclosure describes an approach for managing permissions in a collaborative workspace through a permission user interface presentation. The permissions user interface presentation is provided to the user without losing context with other user interface presentations associated with the collaborative workspace. Further, the permissions user interface presentation visually organizes an existing set of workspace members into two or more groups associated with different respective permission level categories. Permissions can be changed by moving members from one permission level category to another. Further, the permissions user interface presentation provides functionality that allows a user to add new workspace members to the existing set of workspace members. The new members can be selected from either a local system or an alternative system using the same permissions user interface presentation tool.

[0025] By virtue of this approach, a user can effectively discern and modify the permissions associated with the collaborative workspace. The approach also provides a streamlined and user-friendly way to add new members to an existing set of workspace members. More generally, the concepts disclosed herein may address one or more of the challenges or problems previously noted, but are not limited to addressing all or any of these challenges or problems.

[0026] As used herein, the term “user” is used to describe the person who performs the process of managing permissions using the above-summarized approach. The term “members” refers to individuals who are assigned rights to access and interact with the workspace through the permissions. The person who manages permissions (e.g., the user) will typically also be defined as a member, although need not be.

[0027] This disclosure is organized as follows. Section A describes illustrative systems for managing permissions in a collaborative workspace. Section B describes illustrative methods for performing the same function. Section C describes illustrative processing functionality that can be used to implement any aspect of the features described in Sections A and B.

[0028] A. Illustrative Systems

[0029] As a preliminary matter, the various components shown in the figures can be implemented in any manner, for example, by software, hardware, firmware, manual processing operations, and so on, or any combination of these implementations. The phrase “configured to” refers to any way of providing a function, and may encompass any implementation or combination thereof (software, hardware, firmware, manual processing operations, and so on). FIG. 13, to be discussed in turn, provides additional details regarding one illustrative implementation of the functions shown in the figures.

[0030] FIG. 1 shows a workspace-using environment 100. The workspace-using environment 100 includes a workspace-providing system 102. The workspace-providing system 102 provides a collaborative workspace (henceforth simply “workspace”). A workspace defines functionality which allows individuals to work on one or more shared tasks. The workspace includes permissions which define the individuals who are permitted to work on the workspace (referred to as “members” herein). The workspace also includes items (document items, data items, discussion items, etc.) that the members are permitted to work on in a collaborative fashion. In operation, authorized members may engage the workspace to work on the shared items in a coordinated fashion.

[0031] The workspace-providing system 102 includes, or can be conceptualized to include, a collection of components. More specifically, FIG. 1 is a logical depiction of the workspace-providing system 102. In the logical depiction, the components perform different prescribed functions (to be described below). The logical functions may map to physical infrastructure in different ways. For example, the workspace-providing system 102 includes a workspace management module 104. The workspace management module 104 manages the general set-up and operation of a workspace. In doing so, the workspace management module 104 may be conceptualized as providing a main workspace user interface (UI) presentation (as shown in FIG. 3) through which members may interact with the workspace. In a physical implementation, however, these logical functions may be performed by a combination of backend functionality and frontend functionality. For instance, a physical implementation of the workspace-providing system 102 may include a frontend interface component 107 which performs the task of interfacing with members (and which thus implements all of the user interface presentations provided by the workspace-providing system 102, including the workspace UI presentation). Accordingly, reference to the workspace management module 104 should be understood as referring to whatever combination of functionality is used to perform its associated functions, however allocated among one or more components in a physical implementation. The same explanation applies to other logical components within the workspace-providing system 102.

[0032] The workspace management module 104 interacts with a permissions management module 106. The permissions management module 106 allows a user to grant individuals the right to access the workspace, thus assigning these individuals the status of members. The permissions management module 106 also allows the user to define the permission level of members. Illustrative permission levels include an owner permission level, and editor permission level, and a viewer permission level. A member who is assigned an owner permission level enjoys certain administrative rights with respect to the workspace, such as the ability to set up, manage, and terminate the workspace. (In general, the specific set of rights assigned to an owner-member may be environment-specific; for instance, different companies may decide to grant owner-members different respective sets of privileges.) A member who is assigned an editor permission level has the right to make changes to the workspace items. A member who is assigned a viewer permission level has the right to view the workspace items but does not have the right to makes changes to the workspace items.

[0033] The permissions management module 106 provides (or can be logically conceptualized to provide) a permissions UI interface. The permissions UI interface allows the user to specify the permission level of members and add new members to a workspace. As will be described with respect to FIG. 4, the permissions management module 106 displays the permissions UI interface without losing a context associated with the main workspace UI presentation. In other words, the permissions UI interface is displayed inline with respect to the main workspace UI presentation.

[0034] The permissions management module 106 allows the user to add new members from various systems. A system refers to a particular processing environment for performing prescribed tasks. For example, an Email system may correspond to functionality for sending and receiving Email messages. A social networking environment may correspond to functionality for allowing members of a social group to interact with each other via a network (such as the Internet), and so on. A system may be physically implemented using a collection of data processing equipment, such as various server-type computing devices, data stores, and so on.

[0035] FIG. 1 shows an illustrative three systems, system A 108, system B 110, and system n 112, although workspace-providing system 102 can interact with any number of systems. System A 108 is associated with the workspace-providing system 102, and is therefore referred to as a local system herein. That is, system A 108 is “local” to the workspace-providing system 102 because at least parts of the information that it provides are readily accessible to the workspace-providing system 102. The other systems (110, 112) may not be directly associated with the workspace-providing system 102, and are therefore referred to as alternative systems.

[0036] Each system may be associated with different groups of user. For example, assume that system B 110 is an Email system. A user who is operating the workspace-providing system 110 may have an Email account with system B 110. The user may also maintain a collection of Email contacts in system B. Accordingly, these contacts define a group of individuals associated with system B (from the vantage point of the user who is interacting with the workspace-providing system 102). Individuals who are associated with an alternative system (such as alternative system B 110) are referred to herein as “alternative persons.” Individuals who are associated with the local system A 108 are referred to as local system persons.

[0037] The permissions management module 106 allows a user to add new members to the workspace who are either local system persons or alternative system persons. To perform this task, the workspace-providing system 102 relies on an interface module 114. The interface module 114 couples the permissions management module 106 to various systems (108, 110, . . . 112). Later figures will be used to explain illustrative ways in which the permissions UI presentation can be used to add local system persons and alternative system persons to a workspace.

[0038] FIG. 1 illustrates one outcome of the above-summarized procedure for adding persons to a workspace. The figure shows that a group of existing or previous members 116 are granted rights to interact with the workspace. The user interacts with the permissions management module 106 to add a group of new members 118 to the workspace. The new members 118 can be culled from any group of persons who are associated with the user, such as local system persons, alternative system persons, or some combination thereof.

[0039] The workspace management module 104 may also interact with an item management module 120. The item management module 120 allows a user to add and remove items from the workspace. Adding an item to a workspace has the effect of “placing” the item in a shared location where it can be accessed and acted upon by members of the workspace (in a manner defined by the respective permissions of the members). The items can include any type of information, including document items (word processing document items, spreadsheet document items, presentation-related document items, and so on), data items, discussion items, and so on. No limitation is placed on what may constitute an item as used herein.

[0040] The workspace management module 104 may also interact with an activity management module 122. The activity management module 122 manages tasks associated with the workspace. For example, the activity management module 122 can be used by the user to set up tasks for one or more workspace members. The activity management module 122 may also provide information regarding tasks that the user is asked to performed. The activity management module 122 can also provide various notifications to members. For example, the activity management module 122 can alert a member regarding who has used (or who has failed to use) the workspace within a specified period of time.

[0041] The workspace management module 104 may also interact with a discussion management module 124. The discussion management module 124 manages communication among workspace members. For instance, the discussion management module 124 can maintain a blog-type message thread which captures the message exchange among members. The discussion management module 124 can allow a member to reply to an existing message, start a new message thread, and so on.

[0042] The enumeration of logical modules in FIG. 1 is illustrative. Other implementations can include additional modules. In addition, or alternatively, an implementation can omit one or more of the modules shown in FIG. 1.

[0043] The result of setting up a workspace will be workspace information. The workspace information defines a linked collection of members, permissions, items, activities, notifications, and so on. A workspace information store 126 can be used to store workspace information 128 associated with different respective workspaces (represented in the figure as ovals). In one case, the workspace store 126 can store an actual copy of the items that are included in a workspace. Alternatively, or in addition, the workspace store 126 can store reference pointers which point to various workplace items that are stored elsewhere. A workspace itself is a logical concept. That is, a workspace corresponds to a logical “space” that is defined by workspace information in conjunction with the functionality used to interact with the workspace information.

[0044] Advancing to FIG. 2, this figure shows one illustrative system 200 that can be used to implement the workspace-providing system 102. The system 200 implements the workspace-providing system 102 in a network environment. In the network environment, members may access the workspace-providing system 102 using respective member electronic devices (202, 204, . . . 206) via a network 208.

[0045] The member electronic devices (202, 204, . . . 206) can correspond to any type of data processing device or any combination of types of data processing devices. For instance, a member electronic device can be implemented by a desktop computer, a laptop computer, a personal data assistant (PDA) device, a mobile communication device, a set-top box, a game console device, and so on. Or the electronic member device can correspond to special-purpose equipment expressly designed for interacting with the workspace-providing system 102. Members may access network-accessible resources using browsing functionality (not shown) provided by the member electronic devices (202, 204, . . . 206).

[0046] The network 208 may represent any type of mechanism for allowing the member electronic devices (202, 204, . . . 206) to interact with the workspace-providing system 102. The network 208 can correspond to a wide area network (such as the Internet), a local area network (LAN), a point-to-point connection, or any combination of connectivity mechanisms. The network 208 can be physically implemented using any combination of hardwired links, wireless links, name servers, gateways, routers, and so on (not shown). The network 208 can be governed by any protocol or combination of protocols.

[0047] In one scenario, the functionality and information associated with a workspace are entirely provided by the workspace-providing system 102 at some network-accessible location (or locations). This means, for instance, that all of the items associated with a workspace may be stored at some network-accessible location (or locations). Alternatively, or in addition, parts of the workspace functionality and/or workspace information can be implemented locally by the member electronic devices (202, 204, . . . 206). For instance, a workspace may include one or more items that are stored locally on one or more member electronic devices (202, 204, . . . 206). The workspace information stored at the workspace-providing system 102 may include reference pointers which point to these items; that is, optionally, the workspace information may not store the items themselves. In another alternative case, part (or all) of the workspace-providing system 102 can be implemented using peer-to-peer (P2P) infrastructure, thus eliminating or reducing the role of a centrally-provided workspace-providing system 102. Still other implementations are possible.

[0048] As mentioned above in connection with FIG. 1, the permissions management module 106 may interact with various systems, such as a local system 108 and various alternative systems (110, . . . 112). FIG. 2 illustrates one implementation of these systems (108, 110, . . . 112). The workspace-providing system 102 is shown as being grouped with the local system 108 to graphically illustrate the affiliation between these two systems. The workspace-providing system 102 is shown as being separate from the various alternative systems (110, . . . 112) to emphasize that the workspace-providing system 102 may not be affiliated with the alternative systems (110, . . . 112). For example, one illustrative alternative system may comprise an Email system. Another illustrative alternative system may comprise a social networking system, and so on. If these alternative systems (110, . . . 112) are implemented in a network environment (as shown), they can be separately accessed at respective network addresses.

[0049] As described above, different systems may be associated with different groups of people. For instance, a local system is associated with a group of local system persons, while an alternative system is associated with a group of alternative system persons. FIG. 2 illustrates this feature by showing that one of the alternative systems includes people information 212 that identifies one or more groups of people.

[0050] FIG. 3 shows a workspace UI presentation 302 that can be provided by the workspace management module 104 (although, as stated above, the workspace-providing system 102 may physically provide the workspace UI presentation 302 using a combination of backend functionality and frontend interface component 107). The workspace UI presentation 302 serves as a main interface through which authorized members may interact with the workspace. In the discussion below, the person who interacts with the workspace UI presentation 302 is referred to as a user.

[0051] The workspace UI presentation 302 includes various component parts. The selection and arrangement of these parts shown in FIG. 3 is representative; other implementations can adopt different selections and arrangements of parts than that shown in the UI-related figures.

[0052] A menu part 304 of the workspace UI presentation 302 allows the user to invoke different functions provided by the workspace UI presentation 302. For instance, a “workspace” option allows the user to select a particular workspace with which to interact. A “documents” option allows the user to view items that can be added to the workspace, and then to select and add such items. A “people” option allows the user to view people who may be added to the workspace, and then to select and add such persons. The menu part 304 can include yet additional options.

[0053] In the representative case of FIG. 3, the user has selected a workspace related to a neighborhood petition regarding a new shopping mall. A title part 306 of the workspace UI presentation 302 identifies a title associated with the workspace, namely “Petition regarding new shopping mall.” A message part 308 of the workspace UI presentation 302 provides a message to the user. In this case, the message is an introductory message which reads “Welcome Julie Brown.” In this representative example, the user, Julie Brown, is an owner of the workspace, which allows her to perform various administrative functions with respect to the workspace.

[0054] A member indicator part 310 of the workspace UI presentation 302 identifies how many members are currently assigned to this workspace. In this example, there are eight members. The user can activate the member indicator part 310, upon which the member indicator part 310 will reveal information that identifies the eight members. An “add file” part 312 of the workspace UI presentation 302 allows a user, upon activation, to add items to the workspace.

[0055] An item presentation part 314 of the workspace defines a space for displaying some of the items associated with the workspace. The item presentation part 314 may represent each item using a graphical icon in combination with the item's file name. This is merely an example. Alternatively, or in addition, for instance, the item presentation part 314 can identify each item by only listing the file name of the item. The user can activate an item by clicking on the item (or activating it in some other way). Once activated, the user can view the item and edit the item (if the user has editing rights). In the example of FIG. 3, all of the items correspond to document items that pertain to the workspace theme, that is, a neighborhood petition.

[0056] A side panel part 316 provides different functions associated with different tabs. FIG. 3 shows three representative tabs in the side panel part 316: an activity tab; a discussion tab; and a clipboard tab. The tabs activate panels for performing associated functions and displaying associated information. Other implementations may include additional tabs, fewer tabs, and/or different types of tabs. The user can remove and restore the side panel part 316 by activating an appropriate command, such as a “hide panel” command and a “restore panel” command, respectively.

[0057] The activity tab activates an activity panel (not shown in FIG. 3). The activity management module 122 can implement the activity panel. The activity panel provides information regarding various tasks that are assigned to the user in connection with the workspace. The activity panel also provides functionality that allows the user to assign new tasks and schedule events. The activity panel may also provide information regarding various notifications generated by the activity management module 122.

[0058] The discussion tab activates a discussion panel (which corresponds to the panel that is activated in FIG. 3). The discussion management module 124 can implement the discussion panel. The discussion panel provides discussion items (less formally, “messages”) pertaining to the workspace. In this case, the discussion items form a thread of messages exchanged among members of the workspace. In one case, the discussion panel can organize the discussion items in a blog-type format, that is, with indentations illustrating the sequence of discussion items in the exchange. The discussion panel may include one or more prompts which enable the user to contribute to the discussion thread, e.g., by replying to an existing discussion item, starting a new discussion thread, and so on. The discussion items in the discussion thread constitute particular types of workspace items, as broadly defined herein.

[0059] The clipboard tab activates a clipboard panel (not shown in FIG. 3). The clipboard panel identifies items that have been stored in the user's clipboard. The user may add any of the items in the clipboard to the workspace, e.g., by moving the items from the clipboard panel to the item presentation part 314 using a drag-and-drop operation or other technique.

[0060] FIG. 4 shows another depiction of the workspace UI presentation 302 (with the side panel part 316 hidden to facilitate illustration). In this case, the user has activated a permissions UI presentation 402. In one scenario, the user invokes the permissions UI presentation 402 by clicking on the member indicator part 310 (illustrated in FIG. 3). This causes the permissions management module 106 to display the permissions UI presentation 402 inline with respect to the workspace UI presentation 302. In other words, the permissions management module 106 displays the permissions UI presentation 402 without losing the context associated with the main workspace UI presentation 302.

[0061] The permissions UI presentation 402 includes plural component parts. A title part 404 of the permissions UI presentation 402 conveys how many people are members of the workspace in question—in this case, there are currently eight such people.

[0062] An owner-identification part 406 provides information that identifies the owner or owners associated with the workspace. In this case, there is only one owner, Julie Brown, who happens to also be the user who is currently interacting with the workspace UI presentation 302. An editor-identification part 408 provides information that identifies editors associated with the workspace. In this case, there are five named members with editing privileges. A viewer-identification part 410 provides information that identifies viewers associated with the workspace. In this case, there are two named viewers. Together, these parts (406, 408, and 410) visually organize the members of the workspace into different groups associated with different respective permission levels. As shown, one or more of the parts (406, 408, 410) can organize the members in columns; in addition, or alternatively, other graphical approaches can be used to organize the members.

[0063] The user can change the permission level of an existing member in various ways. In one technique, the permissions UI presentation 402 can permit the user to drag a member name from one part to another part. For example, assume that the user wants to change the permission level of “Mary Willard” from her current status as an editor to a target status of viewer. The user may single-click on the name “Mary Willard” in the editor-identification part 408 and drag this name to the viewer-identification part 410. The user can alternatively double click on Mary Willard's name in the editor-identification part 408, prompting the permissions UI presentation 402 to display additional information (not shown) regarding Mary Willard, including her permission level. The user can modify this person's permission level by directly making changes to the displayed additional information. Still other techniques can be used change the permission level of exiting members.

[0064] A search part 412 allows the user to search for a member, e.g., by inputting the name of the member being sought as a search term. The permissions management module 106 responds to the search by displaying information regarding the member. The user may choose to perform this search in those circumstances in which a workspace has a relatively large number of members, so that it may be difficult to identify (at quick glance) the member being sought within the full list provided by the permissions UI presentation 402.

[0065] An add people tab 414 can be activated by the user to invoke a process for adding one or more people to the workspace, thus making these people new members of the workspace. Assume that the user activates this tab 414. The permission management module 106 responds by representing an added person panel 502, as shown in FIG. 5.

[0066] More specifically, FIG. 5 shows another depiction of the workspace UI presentation 302 and the permissions UI presentation 402. As stated, the user has activated the “add people” tab 414. This action prompts the presentation of an added person panel 502. In one illustrative implementation, the added person panel 502 displays a group of persons who are associated with the user (Julie Brown) in the context of the local system A 108. Hence, according to the terminology used herein, these people are referred to as local system persons. In other words, the local system persons are individuals who already have an affiliation with the workspace-providing system 102.

[0067] Note that the expanded permissions UI presentation 402 is still displayed inline with respect to the workspace UI presentation 302. In other words, the permissions UI presentation 402, including the added person panel 502, is still displayed without loosing context with the main workspace UI presentation 302.

[0068] The added person panel 502 may include a scroll bar 504 or like mechanism for scanning the list of local system persons. The added person panel 502 also includes a search part 506. The search part 506 allows the user to search for a desired local system person, e.g., by inputting the name of the desired person as a search term. The permissions management module 106 responds to the search by displaying information regarding the desired person, if there is record of such a person.

[0069] Upon locating a desired person, the user can grant that person membership status in the workspace. The permissions UI presentation 402 can accommodate different techniques for performing this function. In one technique, the user can move a desired person from the added person panel 502 to a target permission identification part of the permissions UI presentation 402. For example, assume that the user wishes to grant viewer status to the person “Parker Hill,” who currently is listed as a local system person, but who currently is not a member of the workspace. As shown in FIG. 4, the user can single-click on Parker Hill's name in the added person panel 502 and drag the name into the viewer-identification part 410. This action causes the permission management module 106 to add Parker Hill as a member of the workspace, having a permission level of “viewer.” The permissions UI presentation 402 can also include functionality that allows the user to select multiple names in the added person panel 502 and move the corresponding names as a group to a desired permission identification part of the permissions UI presentation 402.

[0070] Alternatively, the person that the user wants to add to the workspace may not currently exist among the user's local system persons. To address this scenario, the user can activate an “add others” command 508. This invokes a process for adding non-local (“alternative”) system persons to the workspace, as set forth below with respect to FIGS. 6-9.

[0071] Starting with FIG. 6, this figure shows the presentation of an introductory UI presentation 602 that may be invoked when the user activates the “add others” command 508 in the added person panel 502. The introductory UI presentation 602 is displayed without losing the context associated with either the workspace UI presentation 302 or the permissions UI presentation 402.

[0072] The introductory UI presentation 602 includes a system selection part 604. The system selection part 604 provides functionality that allows the user to select an alternative system, e.g., in this merely illustrative case, the user may select from among Email System A, Email System B, Social Network X, Social Network Y, and so on. Each system may maintain information regarding a population of persons associated with the system. For example, assume that the user has previously defined a group of colleagues using a social networking system, such as Social Network X. Assume further that the user desires to grant one of these colleagues membership status in the neighborhood petition workspace. If so, the user can activate the entry for “Social Network X” in the system selection part 604. FIG. 6 illustrates the Social Network X entry with a box around it to graphically represent the fact that is has been selected by the user.

[0073] The introductory UI presentation 602 also includes a user validation part 606. The user validation part 606 can invite the user to enter credential information (e.g., user ID and user password, etc.) to gain admittance to the selected alternative system—in this case, Social Network X.

[0074] Advancing to FIG. 7, assume that the user has entered valid credentials to gain access to the alternative system associated with Social Network X. The permissions management module 106 responds by presenting an alternative person UI presentation 702. The alternative person UI presentation 702 is displayed without losing the context associated with either the workspace UI presentation 302 or the permissions UI presentation 402.

[0075] The alternative person UI presentation 702 includes an alternative person part 704. The alternative person part 704 identifies alternative system persons associated with Social Network X. In the illustrated case shown in FIG. 7, the alternative person part 704 identifies groups of people previously defined by the user within Social Network X, such as “College Pals,” “Neighbors & Such,” and so on. Alternatively, or in addition, the alternative person part 704 can identify individual alternative system persons, that is, by listing these people by individual name. The alternative person part 704 includes a scroll bar 706 for navigating within the list of alternative system persons.

[0076] Assume in this merely illustrative case that the user wishes to add the entire group “Neighbors & Such” to the workspace as new members. In this case, the user can click on a box adjacent to this group and activate an import command 708. Or the user can abort the operation by activating a cancel command 710.

[0077] Assume that the user has activated the import command 708. This causes the permission management module 106 to import all of the alternative system persons in the group “Neighbors & Such” into the user's collection of local system persons, such that everyone in the group “Neighbors & Such” is now identified as a local system person.

[0078] FIG. 8 shows the outcome of the actions taken by the user in FIG. 7. Namely, FIG. 8 again shows the permissions UI presentation 402 which is displayed inline with respect to the main workspace UI presentation 302. In this case, the added person panel 502 has been updated to indicate that the group “Neighbors & Such” has been added to the list of the user's local system persons. The added person panel 502 may display an indicator 802 (e.g., “New!,” etc.) which indicates that the group “Neighbors & Such” has just been added to the list of local system persons.

[0079] At this juncture, the user can proceed in the manner set forth above with respect to FIG. 5. Namely, the user can add the individuals in the group “Neighbors & Such” to the current set of workspace members by dragging the group name “Neighbors & Such” to an appropriate permission identification part (e.g., parts 406, 408, or 410). In illustrated case shown in FIG. 8, the user is in the process of clicking on and dragging the group “Neighbors & Such” to the viewer-identification part 410 of the permissions UI presentation 402. In response to this action, the permissions management module 106 will automatically grant all of the individuals in the designated group the right to view the workspace items (but not edit them). Alternatively, the user may expand the members in the group “Neighbors & Such” within the added person panel 502 and move one or more individual members in that group to the desired permission identification part of the permissions UI presentation 402.

[0080] FIG. 9 shows the result of the actions described above with respect to FIG. 8. In this case, the viewer-identification part 410 has been updated to include all four individuals in the group “Neighbors & Such.” Once again, note that the permissions UI presentation 402 remains inline with respect to the workspace UI presentation 302.

[0081] The above process for adding alternative system persons is illustrative and non-limiting, and can be varied in many ways. For example, in an alternative approach, the permissions management module 106 can permit the user to directly “move” alternative system persons from the alternative person part 704 (of FIG. 7) to the desired permission-identification part (406, 408, or 410), that is, without using the added person panel 502 as a middleman in the operation.

[0082] FIG. 10 shows another depiction of the workspace UI presentation 302, introduced in FIG. 3. Various features in the workspace UI presentation 302 reflect the outcome of the adding process described above. For instance, the message part 308 now alerts the user (Julie Brown) that five new people have been added to the workspace (namely, Parker Hill from the local system person list and the four-person group “Neighbors & Such” from a user group maintained by Social Network X). Similarly, the member indicator part 310 reveals that the workspace now includes thirteen members, five of which are new.

[0083] Finally, note that the user has also activated the clipboard tab of the side panel part 316. This action causes the workspace UI presentation 302 to display the clipboard panel. The user's clipboard panel contains one document item. The user may move this document item into the item identification part 314 in any manner, such as by clicking on and dragging the document item to the item identification part 314. This operation has the effect of adding the identified document item to the set of workspace items, enabling members to view and edit (if permitted) this document item in a shared fashion.

[0084] In general, the process of managing permissions occurs in a user-friendly manner in the same context as other workflow UI presentations. This aspect of the workplace providing system 102 may help integrate the user's permission management experience with the overall flow of workspace activities, potentially making the user's permission management experience less complex and difficult. This aspect, in turn, may encourage the user to define permissions in a relatively fine-grained manner to render the workspace more secure.

[0085] B. Illustrative Flowcharts

[0086] FIGS. 11 and 12 illustrate the operation of the system 100 in flowchart form. To facilitate discussion, certain operations are described in FIGS. 11 and 12 as constituting distinct blocks performed in a certain order. Such implementations are illustrative and non-limiting. Certain blocks described herein can be grouped together and performed in a single operation, and certain blocks can be performed in an order that differs from the order employed in the examples set forth in this disclosure. The blocks shown in the flowcharts can be implemented by software, firmware, hardware, manual processing, any combination of these implementations, and so on.

[0087] As the functions described in the flowcharts have already been set forth above, the following explanation will serve as a summary and review of those functions.

[0088] Starting with FIG. 11, this figure shows a procedure 1100 for interacting with the permissions UI presentation 402 in an inline manner with respect to the workspace UI presentation 302. The procedure 1100 is described from the general vantage point of being executed by the workspace-providing system 102.

[0089] In block 1102, the workspace-providing system 102 provides the workflow UI presentation 302 upon the request of the user.

[0090] In block 1104, the workspace-providing system 102 receives the user's request to manage permissions. In one merely illustrative case, the workspace-providing system 102 can receive such an instruction in response to the user's activation of the member indicator part 310 shown in FIG. 3.

[0091] In block 1106, the workspace-providing system 102 presents the permissions UI presentation 402 to the user. The workspace-providing system 102 presents the UI presentation 402 inline with respect to the workspace UI presentation 302, e.g., without losing the context of the workspace UI presentation 302.

[0092] In block 1108, the workspace-providing system 102 receives an instruction associated with some action that the user wishes to take. For instance, the user may have entered an instruction to change the permission level of an existing member. Or the user may have entered an instruction to add a new member, and so forth.

[0093] In block 1110, assume that the user has entered an instruction to change the permission level of an existing member. In this case, block 1110 carries out this instruction. In one case, the user can change the permission level using a drag-and-drop procedure. In another case, the user can change the permission level by clicking on a name to invoke additional information regarding a member; the user can then make permissions-related changes directly to the additional information.

[0094] In block 1112, assume that the user has entered an instruction to add one or more persons to the workspace. In this case, block 1112 indicates that the procedure 1200 shown in FIG. 12 is invoked.

[0095] Block 1114 generally indicates the receipt (and action upon) some other instruction made by the user.

[0096] FIG. 12 shows a procedure 1200 for adding a member (or members) to a workspace.

[0097] In block 1202, the workspace-providing system 102 presents a list of people associated with the user in the context of the local system. According to the terminology used herein, the people are local system persons. In one implementation, the permissions UI presentation 402 can present a list of local system persons in the added person panel 502.

[0098] In block 1204, the workspace-providing system 102 determines whether the user wants to add one or more existing local system persons to the workspace. In block 1206, assuming that block 1204 is answered in the affirmative, the workspace-providing system 102 receives the user's selection of one or more local system persons. In block 1208, the workspace-providing system 102 adds these selected persons to the workspace. The operations described in blocks 1204-1208 can be implemented using a drag-and-drop procedure. In this procedure, the user may click on a name in the added person panel 502 and drag it to one of the permission-identification parts (406, 408, or 410) of the permissions UI presentation 402.

[0099] Assume that block 1204 is answered in the negative (e.g., the user does not want to add an existing local system person to the workspace at this time). In this case, in block 1210, the workspace-providing system 102 asks whether the user wishes to add an alternative system person to the workspace.

[0100] In block 1212, assuming that block 1210 is answered in the affirmative, the workspace-providing system 102 receives the user's selection of an alternative system. For example, as explained above with respect to FIG. 6, the user may select Social Network X as the alternative system.

[0101] In block 1214, the workspace-providing system 102 can present a collection of alternative system persons associated with the user in the context of the selected alternative system. One example of such a presentation is shown in FIG. 7.

[0102] In block 1216, the workspace-providing system 102 receives the user's selection of one or more alternative system persons. In the merely representative case of FIG. 7, the user has selected the group “Neighbors & Such.”

[0103] In block 1218, the workspace-providing system 102 adds the selected alternative system person to the collection of the user's local system persons. The process then returns to block 1204, where it is determined whether the user now wants to add one or more local system persons to the workspace. Since the selected alternative system person have been imported and relabeled as local system persons, the user is now free to add these people to the workspace from the list of local system persons. Alternatively, the above process can be used to grant a single alternative system person membership status in the workspace.

[0104] C. Representative Processing Functionality

[0105] FIG. 13 sets forth illustrative electrical data processing functionality or equipment 1300 (simply “processing functionality” below) that can be used to implement any aspect of the functions described above. With reference to FIG. 1, for instance, the processing functionality 1300 can be used to implement the workspace-providing system 102 or any component thereof. With reference to FIG. 2, the processing functionality 1300 can also be used to implement any of the user electronic devices (202, 204, . . . 206). With reference to the same figure the processing functionality 1300 can also be used to implement any aspect of the alternative systems 210. The processing functionality 1300 may correspond to a general purpose computing device, a special purpose computing device, or any other implementation.

[0106] The processing functionality 1300 can include volatile and non-volatile memory, such as RAM 1302 and ROM 1304, as well as one or more processing devices 1306. The processing functionality 1300 also optionally includes various media devices 1308, such as a hard disk module, an optical disk module, and so forth. The processing functionality 1300 can perform various operations identified above when the processing device(s) 1306 executes instructions that are maintained by memory (e.g., RAM 1302, ROM 1304, or elsewhere). More generally, instructions and other information can be stored on any computer-readable medium 1310, including, but not limited to, static memory storage devices, magnetic storage devices, optical storage devices, and so on. The term “computer-readable medium” also encompasses plural storage devices. The term “computer-readable medium” also encompasses signals transmitted from a first location to a second location, e.g., via wire, cable, wireless transmission, etc. The term “logic” describes instructions for performing identified tasks; for example, the permissions management module 106 can be implemented by logic for managing permissions, and this logic may correspond to instructions associated with tasks performed by the permissions management module 106 as described above.

[0107] The processing functionality 1300 also includes an input/output module 1312 for receiving various inputs from a user (via input modules 1314), and for providing various outputs to the user (via output modules). One particular output mechanism may include a presentation module 1316 and an associated graphical user interface (GUI) 1318. The processing functionality 1300 can also include one or more network interfaces 1320 for exchanging data with other devices via one or more communication conduits 1322. One or more communication buses 1324 communicatively couple the above-described components together.

[0108] In closing, the description may have described various concepts in the context of illustrative challenges or problems. This manner of explication does not constitute an admission that others have appreciated and/or articulated the challenges or problems in the manner specified herein.

[0109] More generally, although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.