Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: A method and apparatus for inheritance-based propagation is provided. The method comprises receiving a request from a client computer to update an access permission associated with a specific namespace in a nested namespace structure for a user, the specific namespace being associated with a group of users, wherein the nested namespace structure includes one or more child namespaces of the specific namespace; causing updating of the access permission associated with the specific namespace for the user; identifying the specific namespace as the current namespace; and performing an iterative process having the following steps until a termination criterion is satisfied.

Abstract: A method and apparatus for inheritance-based propagation is provided. The method comprises receiving a request from a client computer to update an access permission associated with a specific namespace in a nested namespace structure for a user, the specific namespace being associated with a group of users, wherein the nested namespace structure includes one or more child namespaces of the specific namespace; causing updating of the access permission associated with the specific namespace for the user; identifying the specific namespace as the current namespace; and performing an iterative process having the following steps until a termination criterion is satisfied.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing project tasks using content items. A user can create tasks within a content item. The tasks can be assigned to users and/or be assigned due dates. The content item can be shared with other users such that updates to the content item (e.g., updates to the tasks) can cause sending notifications to users associated with the content item. When a task in the content item is updated, all members of the project can be notified of the updated status of the task. A task list for a project can be created that aggregates tasks from multiple content items associated with the project. Tasks can be organized in the task list according to the content item the task was created in. Updates to tasks in the task list can cause corresponding updates to the tasks in the content items.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects using references between the project and project items. Project items can be, for example, synchronized content items, collaborative content items, other projects, folders, tasks, user accounts, etc. The content management system can create a project identifier for managing data and/or people associated with a project. In various implementations, the content management system can store references between the project and project items in one or more folders associated with the project, in a database, in content item metadata, etc. In some implementations, the storage location of a content item does not affect whether it is associated with the project. When a project is selected by a user, the content management system can generate project view that presents various project items associated with the project in a convenient and easy to access graphical user interface.