Patent Publication Number: US-2023162155-A1

Title: Systems and methods to attribute automated actions within a collaboration environment

Description:
FIELD OF THE DISCLOSURE 
     The present disclosure relates to systems and methods to attribute automated actions within a collaboration environment. 
     BACKGROUND 
     Collaboration environments, sometimes referred to as integrated collaboration environments, may enable users to assign projects, tasks, and/or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which a virtual team of users does its work. A collaboration environment may enable users to work in a more organized and efficient manner. A collaboration environment may integrate features and/or functionality such as web-based conferencing and collaboration, desktop videoconferencing, and/or instant message into a single easy-to-use, intuitive interface. 
     SUMMARY 
     One aspect of the present disclosure relates to a system configured to attribute automated actions within a collaboration environment. Collaboration environments may allow users to automate sequences of actions in response to trigger events. The automated actions and/or trigger events may be user specified and stored in automation records. Automated actions may take place within the collaboration environment and/or outside the collaboration environment (e.g., through one or more external applications). Trigger events may include events taking place within the collaboration environment and/or outside the collaboration environment. Automation of actions may cause confusion for users and/or may cause other errors or difficulties within the collaboration environment. For example, a user implementing another user&#39;s automation record may be unsure or unclear about the source (e.g., the creator) of the automation record. If the creator is unknown, it may be difficult to discuss the purpose of an automated action, discuss occurrence of possible errors, and/or otherwise engage with the creator. A user may create an automation record which may be limited by their own permissions within the system. Accordingly, one or more implementations of the systems and methods presented herein may provide a technique to attribute automated actions within the collaboration environment to creator(s) of the automated actions through presentation of one or more attribution labels. An attribution label may include one or more of a depiction of an avatar of a creator, a name and/or username of the creator, and/or other information. In some implementations, it may be desired to merely provide an indication that one or more actions were carried out via an automation, without necessarily attributing the one or more actions to a specific user/creator. In such instances, an attribution label may indicate that an action was completed through an automation and/or may be devoid of a particular identification of a creator. 
     One or more implementations of a system configured to attribute automated actions within a collaboration environment may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include one or more of attribution information, automation records, and/or other information. The automation records may specify automated actions to carry out in response to trigger events. An individual automation record may define one or more trigger events, one or more automated actions to carry out in response to occurrence of the one or more trigger events, and/or other information. In some implementations, automated actions may be effectuated within a collaboration environment based on trigger events occurring within the collaboration environment. In some implementations, automated actions may be effectuated outside the collaboration environment based on trigger events occurring within the collaboration environment. In some implementations, automated actions may be effectuated within a collaboration environment based on trigger events occurring outside the collaboration environment. In some implementations, automated actions may be effectuated outside a collaboration environment based on trigger events occurring outside the collaboration environment. The attribution information may indicate individual creators of individual automation records and/or may specify other information. 
     The processor(s) may be configured to detect occurrence of the trigger events. By way of non-limiting illustration, an occurrence of the first trigger event may be detected. In some implementations, the first trigger event may be specified by a first automation record. The first automation record may define a first automated action to carry out in response to the first trigger event. 
     The processor(s) may be configured to effectuate automated actions corresponding to detected occurrences of the trigger events. By way of non-limiting illustration, the first automated action may be effectuated in response to the occurrence of the first trigger event. 
     The processor(s) may be configured to effectuate presentation of attribution labels for effectuated ones of the automated actions. The attribution labels may be generated based on the attribution information. By way of non-limiting illustration, presentation may be effectuated of a first attribution label for the first automated action. In some implementations, the first attribution label may include one or more of an avatar of a first creator of the first automation record, a username and/or name of the first creator of the first automation record, and/or other information. In some implementations, the first attribution label may be devoid of an indication of the first creator. 
     As used herein, any association (or relation, or reflection, or indication, or correspondence) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1). 
     As used herein, the term “obtain” (and derivatives thereof) may include active and/or passive retrieval, determination, derivation, transfer, upload, download, submission, and/or exchange of information, and/or any combination thereof. As used herein, the term “effectuate” (and derivatives thereof) may include active and/or passive causation of any effect. As used herein, the term “determine” (and derivatives thereof) may include measure, calculate, compute, estimate, approximate, generate, and/or otherwise derive, and/or any combination thereof. 
     These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG.  1    illustrates a system configured to attribute automated actions within a collaboration environment, in accordance with one or more implementations. 
         FIG.  2    illustrates a method to attribute automated actions within a collaboration environment, in accordance with one or more implementations. 
         FIG.  3    illustrates an exemplary user interface, in accordance with one or more implementations. 
         FIG.  4    illustrates an exemplary user interface, in accordance with one or more implementations. 
         FIG.  5    illustrates an exemplary user interface, in accordance with one or more implementations. 
     
    
    
     DETAILED DESCRIPTION 
       FIG.  1    illustrates a system  100  configured to attribute automated actions within a collaboration environment, in accordance with one or more implementations. One or more implementations of the systems and methods presented herein may provide a technique to attribute automated actions to creator(s) of the automated actions through presentation of one or more attribution labels. An attribution label may include one or more of a depiction of an avatar of a creator, a name of the creator, a username of the creator, and/or other information. In some implementations, it may be desired to merely provide an indication that one or more actions were carried out via an automation (as opposed to manually by a user), without necessarily attributing the one or more actions to a specific user/creator. In such instances, an attribution label may indicate that an action was completed through an automation and/or may be devoid of a particular identification of a creator (e.g., via an avatar, a name, a username, and/or other information). 
     In some implementations, system  100  may include one or more of one or more servers  102 , one or more client computing platforms  104 , one or more external resources  126 , and/or other components. Server(s)  102  may be configured to communicate with one or more client computing platforms  104  according to a client/server architecture and/or other architectures. Client computing platform(s)  104  may be configured to communicate with other client computing platforms via server(s)  102  and/or according to a peer-to-peer architecture and/or other architectures. Users may access system  100  via client computing platform(s)  104 . 
     In some implementations, individual external resources of one or more external resources  126  may include individual applications providing one or more services outside of system  100 . An application may include one or more of a calendar application, a payment application, an electronic communication application, a social media application, restaurant-reservation application, on-demand delivery application, a project management application, a customer relationship management application, a ticketing application, a partner relationship management application, a web form application, and/or other applications outside of the system providing one or more services. 
     Server(s)  102  may include one or more of non-transitory electronic storage  128 , one or more processors  130  configured by machine-readable instructions  106 , and/or other components. Machine-readable instructions  106  may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions  106  may cause server(s)  102  to facilitate attributing automated actions within a collaboration environment. The instruction components may include one or more of an environment state component  108 , an automation component  110 , an attribution component  112 , a user interface component  114 , and/or other instruction components. 
     Environment state component  108  may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. Managing may include one or more of obtaining, sending, receiving, storing, updating, deleting, archiving, reporting, and/or other processes. The environment state information may include one or more of values of one or more environment parameters, permission records, automation records, attribution information, and/or other information. The environment parameters may include one or more of user parameters, work unit parameters, work status parameter(s), and/or other parameters. The values of the user parameters may specify user information and/or other information. The values of the work unit parameters may specify work information and/or other information. 
     The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters associated with the users interacting with and/or viewing the collaboration environment may include information describing the users, user actions of the users within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment. 
     The values of the user parameters may, by way of non-limiting example, specify one or more of: a legal name, a username, a group parameter, a user account, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more work unit records), one or more portfolios of projects, one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), a presence parameter (e.g., indicating presence and/or interaction level at an environment level, unit of work level, project level, task level, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more units of work the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, and/or other information for the given user. 
     The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given unit of work may have one or more assignees and/or team members working on the given unit of work. Units of work may include one or more of projects, tasks, sub-tasks, to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. 
     By way of non-limiting illustration, the one or more work unit parameters may include one or more of a work assignment parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users. 
     In some implementations, the units of work may be described based on one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date, a completion date, and/or dates), one or more members associated with a unit of work (e.g., a creator, one or more other project/task members, member access information, an assignor, an assignee, and/or other information), a status parameter (e.g., an update, a hardcoded status update, a completed/uncomplete/mark complete, a measured status, a progress indication, quantity of sub-work units remaining for a given unit of work, completed units of work in a given project, and/or other status parameter), one or more user comment parameters (e.g., permission for who may comment such as a creator, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hardcoded responses; and/or other parameters.), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, a given unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more file attachments, notification settings, privacy settings, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.,), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), dependencies between one or more units of work, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other values of work unit parameters. 
     The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more units of work to themselves and/or an other user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users. 
     In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date). 
     In some implementations, user actions within the collaboration environment may include effectuating one or more changes in one or more values of one or more of the environment parameters. User actions may be facilitated through a user interface presenting the collaboration environment. By way of non-limiting illustration, a user action may include marking a unit of work “complete.” Marking a unit of work complete may change a value of a work unit parameter for the unit of work from “incomplete” to “marked complete.” User actions may include other changes to other values of other environment parameters described herein. 
     The environment state information may include individual work status values of a work status parameter of the individual users. An individual work status value of the work status parameter of an individual user may specify whether the individual user is active or inactive in the collaboration environment. In some implementations, “active” may refer to a user who is currently employed. In some implementations, “inactive” may refer to a user who is no longer employed, on a leave of absence, and/or other considerations. By way of non-limiting illustration, the environment state information may include a first work status value for a first creator of a first automation record. 
     In some implementations, individual sets of automated actions and associated individual trigger events may be stored in individual automation records. A set of automated actions may include one or more automated actions. In some implementations, the term “creator” may refer to a user of the system  100  who has created an automation record. An automation record may define one or more of individual actions, individual trigger events, and/or other information. Individual actions may be defined by a target component, an action component, and/or other information. The target component of an automation record may include the environment parameter (or parameters) to which an action is to be carried out on and/or an external resource to which the action is to be carried out with. The action component of an automation record may define what change is to be made on the environment parameter(s) and/or instructions to effectuate the action by the external resource defined by the target component. 
     In some implementations, effectuating individual automated actions outside the collaboration environment may include communicating instructions to effectuate the action to an external resource outside the collaboration environment. In some implementations, effectuating automated actions outside the collaboration environment may include performing an application programming interface (API) call and/or other interaction with the external resource to cause the external resource to execute one or more routines in accordance with the instructions. An API interaction may include one or more of Remote Procedure Call, Representational State Transfer, GraphQL, and/or other interactions. 
     Individual trigger events may be defined by a source component, an event component, and/or other information. The source component of an automation record may include the environment parameter(s) and/or external resource(s) from which occurrences of a trigger event may be derived. The event component may include the value (or change in the value) for the environment parameter(s) and/or the information indicating occurrence of an event within the external resource defined by the source component from which occurrences of a trigger event may be derived. 
     Information indicating occurrence of trigger events outside the collaboration environment may be obtained by virtue of individual external resources communicating the information to system  100 . The communicated information may include status reports and/or other information. In some implementations, the communication of the information may be based on the system  100  sending requests for the information. In some implementations, the communication of the information may be based on individual external resources performing scheduled and/or predetermined reporting protocols (e.g., push notifications and/or other protocols). 
     In some implementations, individual automation records may store counts of occurrences of individual trigger events and/or occurrences of carrying out individual automated actions in the sets of automated actions. 
     In some implementations, individual automation records may include individual automation status values of an automation status parameter of the individual automation records. An individual automation status value of the automation status parameter of an individual automation record may specify whether the individual automation record is active or disabled. An automation status value of “active” may mean that an automation record may be effectuated. An automation status value of “disabled” may mean that an automation record may not be effectuated. 
     The automation component  110  may be configured to determine whether individual automation records are active or disabled based on individual automation status values of the automation status parameter. The individual automation status values of the automation status parameter of the individual automation records may be determined based on the individual work status values of the work status parameter of the individual creators. By way of non-limiting illustration, responsive to the first work status value specifying the first creator is active in the collaboration environment, a first automation status value of the first automation record may specify the first automation record is active. By way of non-limiting illustration, responsive to the first work status value specifying the first creator is inactive in the collaboration environment, the first automation status value of the first automation record may specify the first automation record is disabled. 
     In some implementations, the automation component  110  may be configured to reassign individual automation records to other individual users responsive to the individual work status values specifying the individual creators are inactive in the collaboration environment. The other users may include users having the individual work status values specifying they are active in the collaboration environment. The other users may include users having the same or similar role as the inactive user. By way of non-limiting illustration, responsive to the first work status value specifying the first creator is inactive in the collaboration environment, the automation component  110  may be configured to reassign the first automation record to a second user having a second work status value specifying the second user is active in the collaboration environment. In some implementations, the automation component  110  may be configured to effectuate communication of one or more notifications to the newly reassigned users prior to, during, and/or after the reassignment. Notifications may be communicated within system  100  (e.g., internal message and/or notification) and/or outside of system  100  (e.g., email, SMS message, and/or other considerations). 
     Permission records for individual users may specify individual sets of permissions within the collaboration environment and/or outside the collaboration environment. An individual permission record for an individual user may specify whether the individual can carry out certain actions within the collaboration environment and/or outside the collaboration environment. If a user is deemed to have permission, the user may be permitted to carry out the actions within the collaboration environment and/or outside the collaboration environment. If a user is deemed to not have permission, the user may not be permitted to carry out the actions within the collaboration environment and/or outside the collaboration environment. 
     One or more permissions to carry out certain actions within the collaboration environment may refer to one or more of ability to access one or more records (e.g., user record, work unit record, automation record, and/or other records), ability to change one or more values of one or more environment parameters (e.g., perform a state change), ability to change, set, and/or otherwise specify one or more environment parameters to one or more specific values (e.g., perform a particular data state change), and/or other actions within the collaboration environment. By way of non-limiting illustration, a set of permissions of the first creator may specify one or more of a first permission, a second permission, a third permission, and/or other permissions. In some implementations, the first permission may specify the first creator has access to a first user record, the second permission may specify the first creator does not have the ability to change the value of a first work unit parameter, and/or the third permission may specify the first creator does have the ability to set values of a second work unit parameter to one or more of a first value, a second value, a third value, or a fourth value (but no other values). It is noted that the above description of permission within the collaboration environment is for illustrative purposes only and not to be considered limiting. Permissions within the collaboration environment may relate to other parameters described herein and/or other features and/or functionality within the scope of this disclosure. 
     One or more permissions to carry out certain actions outside the collaboration environment may refer to one or more of ability to access one or more external resources  126 , ability to cause one or more external resources  126  to perform one or more actions, ability to cause one or more specific actions to be carried out by one or more external resources  126 , and/or other actions outside the collaboration environment. By way of non-limiting illustration, the set of permissions of the first creator may further specify one or more of a fourth permission, a fifth permission, a sixth permission, and/or other permissions. In some implementations, the fourth permission may specify the first creator does not have access to a payment application, the fifth permission my specify the first creator has the ability to control a project management application, and/or the sixth permission may specify the first creator has the ability to perform a specific action in a social media application (e.g., the specific action being post content, but not comment, follow, etc.). It is noted that the above description of permission outside the collaboration environment is for illustrative purposes only and not to be considered limiting. Permissions outside the collaboration environment may relate to other external applications and/or other features and/or functionality within the scope of this disclosure. 
     The attribution information may indicate individual creators of individual automation records. In some implementations, the attribution information may include one or more transparency values of a transparency parameter and/or other information. An individual transparency value of the transparency parameter may specify whether individual automated actions are attributed to the individual creators of the individual automation records. By way of non-limiting illustration, the attribution information may indicate the first creator of the first automation record and/or other information. The attribution information may include a first transparency value of the transparency parameter for the first creator. In some implementations, the first transparency value may specify the first automated action is attributed to the first creator. In some implementations, the first transparency value may specify the first automated action is not attributed to the first creator. 
     The automation component  110  may be configured to generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface. The automation information may specify sets of automated actions to carry out in the collaboration environment in response to occurrence of trigger events. The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. The generation of automation information may result in the creation of individual automation records. 
     The automation component  110  may be configured to detect occurrence of the trigger events based on changes in the values of the environment parameters and/or other information. Detection may be based on monitoring environment state information, user actions, and/or other components of system  100 . In some implementations, individual trigger events may be specified as individual occurrences of change of the values of the environment parameters. Occurrences of change may convey a state change of an environment parameter. The state change may not consider what the change is, but instead that a change occurred. For example, a trigger event may include an occurrence of a reassignment of a unit of work from one user to an other user. 
     In some implementations, individual trigger events may be specified as individual values of the environment parameters. Changes to specific values may be referred to as data state changes. The data state change may refer to a change of a parameter to a specific value from an other value (and/or from a state of being unspecified). For example, a trigger event may include an occurrence of a reassignment of a unit of work from one user to another specific user. For example, a trigger event may include a comment having one or more specific words and/or phrases. 
     The automation component  110  may be configured to obtain information indicating occurrence of trigger events outside the collaboration environment. In some implementations, information indicating occurrence of trigger events outside the collaboration environment may be obtained by virtue of individual external resources communicating the information to system  100 . The communicated information may include status reports and/or other information. In some implementations, the communication of the information may be based on automation component  110  sending requests for the information. In some implementations, the communication of the information may be based on individual external resources performing scheduled and/or predetermined reporting protocols (e.g., push notifications and/or other protocols). 
     By way of non-limiting illustration, automation component  110  may be configured to detect an occurrence of a first trigger event. The first trigger event may be defined by the first automation record defining a first automated action and/or other automated actions to carry out in response to the first trigger event. 
     The automation component  110  may be configured to, responsive to the detection of the occurrence of individual trigger events, effectuate individual automated actions and/or sets of automated actions. By way of non-limiting illustration, automation component  110  may be configured to effectuate first automated action and/or other actions in response to the occurrence of the first trigger event and/or other events. 
     In some implementations, an individual automated action may include effectuating one or more of creation of, change in, and/or specification of, one or more values of one or more of the environment parameters. In some implementations, the creation of, change in, and/or specification of values of environment parameters may be accomplished by accessing a corresponding record (e.g., user record, work unit record, and/or other records). In some implementations, creation of, change in, and/or specification of an individual value may be reflected in views of the collaboration environment accessed by users. The views in the collaboration environment showing the creation of, change in, and/or specification of an individual value may further include views of attribution labels (see, e.g., attribution component  112 ). 
     In some implementations, an individual automated action may be carried out simultaneously (or near simultaneously) with an individual detection of an individual occurrence of an individual trigger event and/or within a specified time frame following an individual detection of an individual occurrence of an individual trigger event. In some implementations, a specified time frame may include a “waiting” period of time before an action is carried out. In some implementations, the waiting period of time may be satisfied by one or more of the passage of the period of time, some other trigger event, and/or other events and/or actions within the collaboration environment. 
     In some implementations, a set of automated actions may be associated with one or more of a sequence in which automated actions in the set are to be carried out, concurrent carrying out of two or more of the automated actions in the set, and/or other features and/or functionality. The automated actions within a set of automated actions may have a specified ordered sequence in which the automated actions are to be carried out. In some implementations, one or more actions may be followed by, and/or preceded by, a specified waiting period. A set of automated actions may specify that two or more actions may be carried out concurrently. 
     In some implementations, automated actions outside the collaboration environment may be effectuated by communicating instructions to an external resource outside the collaboration environment. In some implementations, effectuating individual sets of automated actions outside the collaboration environment may include performing an application programming interface (API) call and/or other interactions with the external resource to cause the external resource to execute one or more routines in accordance with the instructions. An API interaction may include one or more of Remote Procedure Call, Representational State Transfer, GraphQL, and/or other interactions. 
     It is noted that while some descriptions presented herein may be directed to an individual trigger event causing an individual set of automated actions to be carried out within the collaboration environment, this is for illustrative purposes only and not to be considered limiting. For example, in some implementations, multiple trigger events may be combined together through some logic criteria, that when satisfied, may cause an individual set of automated actions to be carried out within the collaboration environment. Logic may include, for example, Boolean logic. By way of non-limiting illustration, logic operators such as “AND”, “OR”, “NOT”, and/or other operations may be utilized to generate more complex trigger combinations for sets of automated actions. In some implementations, the use of logic operators may allow for fewer discrete trigger events to be defined yet still have more complex behavior available to users. For example, there may not need to specify a trigger event of “when task is unassigned”, since through the use of a logic operator “NOT”, a trigger event may be defined by “when task assigned” combined with the operator “NOT”. Further, the Boolean logic may facilitate multistage automation. By way of non-limiting illustration, instead of input “than-if-then” or “if-and-if-then”, logic may include “if-then-then” and/or other operators. In some implementations, a user may specify a set, or pool, of trigger events to trigger one or more automated actions. In some implementations, user may specify that one or more of the trigger events in the set may individually and/or in combination trigger the one or more automated actions. This way, a user may specify multiple options of trigger events which may trigger one or more automated actions. Further, an individual trigger event may trigger multiple automated actions. 
     Attribution component  112  may be configured to effectuate presentation of attribution labels for effectuated ones of the automated actions. Individual attribution labels may be presented on a user interface displaying the collaboration environment. An attribution label may include one or more of a graphical icon, text, and/or other information. The individual attribute labels may be presented on the user interface reflecting the effectuated ones of the automated actions. In some implementations, attribution labels may include identifications of creators and/or other information. An attribution label may include an identification of a creator by one or more of a depiction of an avatar of a creator, a name and/or username of the creator, and/or other information. In some implementations, an attribute label may identify a current user (sometimes referred to as an “owner”) of the automation record (e.g., a user implementing an automation record as part of their workflow). 
     In some implementations, an attribution label may be devoid of an identification of a creator. An attribution label devoid of an identification of a creator may include default information. The default information may include one or more of a depiction of a generic avatar (e.g., not associated with a creator and/or other users), text, and/or other information. Text may include words and/or phrases. A phrase may include, for example, “This is an automated action” and/or variations thereof. 
     By way of non-limiting illustration, attribution component  112  may be configured to effectuate presentation of a first attribution label for the first automated action. In some implementations, the first attribution label may include an identification of the first creator. In some implementations, the first attribution label may include an identification of the first creator by one or more of a depiction (e.g., graphical icon) of an avatar of the first creator, a name and/or username of the first creator, and/or other information. In some implementations, the first attribution label may be devoid of an identification of the first creator. 
     The attribution labels may be generated based on one or more of attribution information, permission records, and/or other information. 
     In some implementations, transparency values of the transparency parameter included in the attribution information may specify whether individual automated actions are attributed to the individual creators of the individual automation records. By way of non-limiting illustration, responsive to the first transparency value specifying the first automated action is attributed to the first creator, the first attribution label may include an identification of the first creator. By way of non-limiting illustration, responsive to the first transparency value specifying the first automated action is not attributed to the first creator, the first attribution label may be devoid of an identification of the first creator. 
     The attribution component  112  may be configured to access permission records of the individual creators of the individual automation records to determine attribution labels. The attribution component  112  may be configured to determine whether the individual automated actions and/or other components of the individual automation records fall within the individual sets of permissions of the individual creators. “Falling within” the individual sets of permission may refer to an automated action being able to be carried out by virtue of an individual user having a specific permission which would allow the automated action to be carried out. If an individual user does have a specific permission which would allow the automated action to be carried out, a determination may be made that an automated action falls within a set of permissions. If an individual user does not have a specific permission which would allow the automated action to be carried out (e.g., but instead generally has permission to carry out the automated action and/or is otherwise not restricted), a determination may be made that an automated action does not fall within a set of permissions. If an automated action falls within a set of permissions, this may be considered a “private” automation record. If an automated action does not fall within a set of permission, this may be considered a “public” automation record. If an automated action falls within a set of permissions, the automated action may be attributed to the particular user. If an automated action does not fall within a set of permission, the automated action be devoid of an attribution to the particular user. 
     Determining whether the individual automated actions of the individual automation records fall within the individual sets of permissions may include comparing individual components of an automation record (e.g., one or more of target component, an action component, a source component, an event component, and/or other information) with individual permissions. In some implementations, when one or more of the components of an automation record are specifically allowed due to one or more permissions in the set of permissions of a creator, it may be determined that individual automated actions of the automation record fall within the set of permissions. In some implementations, when one or more of the components of an automation record are not specifically allowed by one or more permission in the set of permissions of a creator, it may be determined that individual automated actions of the automation record do not fall within the set of permissions. 
     It is noted that the above description of determining whether the individual automated actions and/or other components of the individual automation records fall within the individual sets of permissions of the individual creators is different from determining whether the individual automated actions are affirmatively restricted by one or more permissions. In such a case, the automation record would be considered void insofar that the process of determining whether to attribute actions of the record to a creator would be irrelevant (up to and/or until the automation record is corrected to be valid). 
     The attribution component  112  may be configured to generate the attribution labels based on the determination of whether the individual automated actions of the individual automation records fall within the individual sets of permissions of the individual creators. 
     In some implementations, responsive to determinations that the individual automated actions of the individual automation records fall within the individual sets of permissions of the individual creators, attribution component  112  may be configured to generate the attribution labels to include the identifications of the individual creators. By way of non-limiting illustration, responsive to a determination that the first automated action falls within the first permission of the first creator, the first attribution label may include an identification of the first creator. 
     In some implementations, responsive to determinations that the individual automated actions of the individual automation records do not fall within the individual sets of permissions of the individual creators, attribution component  112  may be configured to generate the attribution labels to be devoid of the identifications of the individual creators. By way of non-limiting illustration, responsive to a determination that the first automated action does not fall within the first permission of the first creator, the first attribution label may be devoid of an identification of the first creator. 
     User interface component  114  may be configured to effectuate presentation of individual user interfaces on individual client computing platforms of one or more client computing platforms  104 . Individual client computing platforms may access a user interface over network  116 . A given user interface may be configured to facilitate one or more of presentation of the collaboration environment, specification of sets of automated actions and/or trigger events, specification of transparency values, and/or other information. 
     The user interface component  114  may be configured to effectuate presentation of a user interface through which users may specify and/or select one or more of one or more automated actions, one or more trigger events, one or more transparency values, and/or other information. 
     A user interface may include one or more user interface portions. A user interface may include one or more input portions, one or more display portions, and/or other components. Individual portions may include one or more user interface elements configured to facilitate user interaction with the user interface. By way of non-limiting illustration, user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other elements configured to facilitate user interaction. 
     A display portion may include views of the collaboration environment. In some implementations, views of the collaboration environment may reflect units of work and/or one or more of creation of, change in, and/or specification of one or more values of environment parameters. In some implementations, views of the collaboration environment may include one or more dashboards displaying units of work. A dashboard may include a timeline and/or Gantt chart view of one or more units of work. The units of work may be arranged by date according to a timeline. A timeline may include a graphical representation of the passage of time via a series of hours, days, weeks, months, and/or years. In some implementations, a dashboard may include one or more unit of work views. A unit of work view may include a display window providing a representation of a unit of work. A unit of work view may display values of one or more work unit parameters of the unit of work. By way of non-limiting illustration, a unit of work view may include a set of display portions and/or input portions. The set of display portions may include individual portions including values of individual work unit parameters. By way of non-limiting illustration, a unit of work view may include one or more of a first display portion displaying a name of the unit of work, a second display portion displaying a description of the unit of work, a third display portion displaying a due date of the unit of work, a fourth display portion showing a comment thread of the unit of work, and/or other information. 
     In some implementations, individual attribution labels many be presented on a user interface displaying the collaboration environment. In some implementations, the individual attribute labels may be presented at individual portions of the user interface reflecting the effectuated ones of the automated actions. By way of non-limiting illustration, a new unit of work may be created through an automation record. The new unit of work may be viewable in a display window of a unit of work view of the collaboration environment. An attribution label may be presented in the display window. By way of non-limiting illustration, a unit of work may be marked complete through an automation record. A timeline view showing the unit of work along a timeline may automatically change to remove the view of the unit of work in response to being marked complete. An attribution label may be presented at or near the timeline indicating that that the unit of work has been marked complete through an automation record and/or may indicate a creator of the automation record. 
       FIG.  3    illustrates an exemplary user interface  300 , in accordance with one or more implementations. The user interface  300  may be configured to obtain user entry and/or selection of automation information, transparency values, and/or other information. The user entry and/or selection may be in the form of specification of automated actions, trigger events, specific transparency values (e.g., indicating a “yes” or a no”), and/or other information. Automated actions may be specified based on entry and/or selection of environment parameters to carry out actions on, entry and/or selection of values to apply to the entered and/or selected environment parameters, and/or other information. Trigger events may be specified based on one or more of entry and/or selection of environment parameters associated with trigger events, entry and/or selection of values of environment parameters associated with trigger events, and/or other information. 
     The user interface  300  may include a trigger input portion  304  to obtain entry and/or selection of a trigger event. The trigger input portion  304  may include a user interface element  308  configured to obtain information identifying a unit of work associated with the trigger event, a user interface element  310  configured to obtain entry and/or selection of an environment parameter associated with the trigger event, and a user interface element  312  configured to obtain entry and/or selection of a value for the environment parameter associated with the trigger event. For illustrative purposes, the trigger event in  FIG.  3    may refer to the status of the task named “Task1” being “marked complete.” 
     The user interface  300  may include an automated action input portion  314  to obtain entry and/or selection of a set of automated actions. The automated action input portion  314  may include a user interface element  316  configured to obtain entry and/or selection of a first environment parameter associated with a first automated action and a user interface element  320  configured to obtain entry and/or selection of a first value for the first environment parameter. For illustrative purposes, the first environment parameter may include a work unit parameter for creating a unit of work and the first value may include a name value of “Task2.” Accordingly, the first automated action may refer to creating a unit of work with the name “Task2” in response to “Task1” being “marked complete.” 
     The user interface  300  may include a transparency input portion  318  to obtain entry and/or selection of a transparency value for the current automated action. The transparency input portion  318  may include a user interface element  322  configured to obtain entry and/or selection of a first value (e.g., “yes” meaning the automated action will be attributed to the creator, a user interface element  324  configured to obtain entry and/or selection of a second value (e.g., “no” meaning the automated action may not be attributed to the creator), and/or other elements. 
     It is noted that  FIG.  3    is for illustrative purposes only and is not to be considered limiting. Instead, it is to be understood that the user interface  300  may be configured in other ways and/or including other elements in accordance with one or more implementations of the system  100  presented herein. 
       FIG.  4    illustrates an exemplary user interface  400  showing an attribution label  410  devoid of an identification of a creator, in accordance with one or more implementations. User interface  400  may include a unit of work view within a collaboration environment. User interface  400  may be a unit of work view showing a unit of work (e.g., “Task X”) which may have been created and/or assigned to a user (e.g., User A) by virtue of one or more automated actions of an automation record. The user interface  400  may include one or more of a first display portion  402  displaying a name of the unit of work, a second display portion  404  displaying an assignee of the unit of work, a third display portion  406  displaying a due date of the unit of work, a fourth display portion  408  displaying a description of the unit of work, attribution label  410 , and/or other information. The attribution label  410  may be devoid of an identification of a creator of the automation record and instead may include default information and/or other information. The default information may include a phrase. 
       FIG.  5    illustrates an exemplary user interface  500  showing an attribution label  510  including of an identification of a creator, in accordance with one or more implementations. User interface  500  may include a unit of work view within a collaboration environment. User interface  500  may be a unit of work view showing a unit of work having a due date which may have been automatically changed by virtue of one or more automated actions of an automation record created by a user (e.g., User B). The user interface  500  may include one or more of a first display portion  502  displaying a name of the unit of work, a second display portion  504  displaying an assignee of the unit of work, a third display portion  506  displaying a due date of the unit of work, a fourth display portion  508  displaying a description of the unit of work, attribution label  510 , and/or other information. The attribution label  510  may include an identification of the creator by virtue of the attribute label  510  identifying the creator by username (e.g., User B). 
     Returning to  FIG.  1   , in some implementations, server(s)  102 , client computing platform(s)  104 , and/or external resource(s)  126  may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network  116  such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s)  102 , client computing platform(s)  104 , and/or external resource(s)  126  may be operatively linked via some other communication media. 
     A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system  100  and/or external resource(s)  126 , and/or provide other functionality attributed herein to client computing platform(s)  104 . By way of non-limiting example, the given client computing platform  104  may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms. 
     External resource(s)  126  may include sources of information outside of system  100 , external entities participating with system  100 , and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s)  126  may be provided by resources included in system  100 . 
     Server(s)  102  may include electronic storage  128 , one or more processors  130 , and/or other components. Server(s)  102  may include communication lines, or ports to enable the exchange of information with a network  116  and/or other computing platforms. Illustration of server(s)  102  in  FIG.  1    is not intended to be limiting. Server(s)  102  may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s)  102 . For example, server(s)  102  may be implemented by a cloud of computing platforms operating together as server(s)  102 . 
     Electronic storage  128  may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage  128  may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s)  102  and/or removable storage that is removably connected to server(s)  102  via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage  128  may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage  128  may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage  128  may store software algorithms, information determined by processor(s)  130 , information received from server(s)  102 , information received from client computing platform(s)  104 , and/or other information that enables server(s)  102  to function as described herein. 
     Processor(s)  130  may be configured to provide information processing capabilities in server(s)  102 . As such, processor(s)  130  may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s)  130  is shown in  FIG.  1    as a single entity, this is for illustrative purposes only. In some implementations, processor(s)  130  may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s)  130  may represent processing functionality of a plurality of devices operating in coordination. Processor(s)  130  may be configured to execute components  108 ,  110 ,  112 ,  114 , and/or other components. Processor(s)  130  may be configured to execute components  108 ,  110 ,  112 , and/or  114 , and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s)  130 . As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components. 
     It should be appreciated that although components  108 ,  110 ,  112 , and/or  114  are illustrated in  FIG.  1    as being implemented within a single processing unit, in implementations in which processor(s)  130  includes multiple processing units, one or more of components  108 ,  110 ,  112 , and/or  114  may be implemented remotely from the other components. The description of the functionality provided by the different components  108 ,  110 ,  112 , and/or  114  described below is for illustrative purposes, and is not intended to be limiting, as any of components  108 ,  110 ,  112 , and/or  114  may provide more or less functionality than is described. For example, one or more of components  108 ,  110 ,  112 , and/or  114  may be eliminated, and some or all of its functionality may be provided by other ones of components  108 ,  110 ,  112 , and/or  114 . As another example, processor(s)  130  may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components  108 ,  110 ,  112 , and/or  114 . 
       FIG.  2    illustrates a method  200  to attribute automated actions within a collaboration environment, in accordance with one or more implementations. The operations of method  200  presented below are intended to be illustrative. In some implementations, method  200  may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method  200  are illustrated in  FIG.  2    and described below is not intended to be limiting. 
     In some implementations, method  200  may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method  200  in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method  200 . 
     An operation  202  may manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include one or more of attribution information, automation records, and/or other information. The automation records may specify automated actions to carry out in response to trigger events. An individual automation record may define one or more trigger events, one or more automated actions to carry out in response to occurrence of the one or more trigger events, and/or other information. In some implementations, automated actions may be effectuated outside the collaboration environment based on trigger events occurring within the collaboration environment. In some implementations, automated actions may be effectuated within a collaboration environment based on trigger events occurring outside the collaboration environment. In some implementations, automated actions may be effectuated outside a collaboration environment based on trigger events occurring outside the collaboration environment. The attribution information may indicate individual creators of individual automation records and/or may specify other information. Operation  202  may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component  108 , in accordance with one or more implementations. 
     An operation  204  may detect occurrence of trigger events. By way of non-limiting illustration, an occurrence of the first trigger event may be detected. In some implementations, the first trigger event may be specified by a first automation record. The first automation record may define a first automated action to carry out in response to the first trigger event. Operation  204  may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component  110 , in accordance with one or more implementations. 
     An operation  206  may effectuate automated actions corresponding to detected occurrences of the trigger events. By way of non-limiting illustration, the first automated action may be effectuated in response to the occurrence of the first trigger event. Operation  206  may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component  110 , in accordance with one or more implementations. 
     An operation  208  may effectuate presentation of attribution labels for effectuated ones of the automated actions. The attribution labels may be generated based on the attribution information. By way of non-limiting illustration, presentation may be effectuated of a first attribution label for the first automated action. In some implementations, the first attribution label may include one or more of avatar of a creator of the first automation record, a username and/or name of the creator of the first automation record, and/or other information. In some implementations, the first attribution label may be devoid of an indication of the first creator. Operation  208  may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to attribution component  112 , in accordance with one or more implementations. 
     Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.