Any action taken on a resource is recorded in TCPinpoint as an Activity. Examples include: task completed, document viewed, project created. Activities are listed in activity feed widgets in sidebars of resources. Users will only see activities for resources that they have appropriate permissions for.
There are three types of authority in TCPinpoint: Property Administrator, Project Creator, and Project Administrator. Authorities have different permission sets for viewing and acting on properties, projects, tasks and documents separate from the role-based permission system. Each type of authority is granted in a different way.
Conditions are individual requirements that the team member assigned to a role on a task must meet to consider that task complete. Conditions are children of tasks, and are set in the template builder. There are two types of conditions: 'yes/no' and document upload. A task can be marked as complete without the condition being met, but it will display a green circle with an exclamation mark in the workflow.
A ledger is a flat record of all of the financial information about a project. You have the ability to design as many ledgers as you want because over the course of a project. TCPinpoint gives you the ability to record amounts against each of those ledgers, and you can update additional lines and approve them internally.
A permission is a single rule that states whether a user can or cannot view or take action on a resource. Permissions may refer to groups of rules defined by what authority a user has, what role they have on a project team, or what read-only permissions they have.
A phase is a segment of a workflow; it is a child of a workflow and a parent of a task. A phase is primarily a logical grouping of tasks, and completing all tasks in a phase likely signals a milestone. Phases are set in the template builder.
A Project is the virtual collaboration space for managing an individual tenancy delivery. A project has one workflow, which is defined by the template (chosen during project creation). The project workspace contains tabs to display the workflow, a document library, project team members, information relating to tenant and tenancy, as well as insights to how the project is tracking. Authority users may also see tabs for ledgers and leasing information.
Project Administrator is an authority within TCP, which has a set of permissions separate to role-based permissions. A Project Administrator has full access to all tasks and documents on any project they have administrator authority on. Project Administrators can add people to projects, assign roles to tasks and CC roles on tasks. Project Administrator authority is assigned by Project Creators in the 'team members' tab.
Project Creator is an authority within TCP, with a set of permissions separate to role-based permissions. A Project Creator has full access to all tasks and documents on any project they have created. Project Creators can add team members to their projects, assign roles to tasks and CC roles on tasks. Project Creator authority is assigned to the user who has started a project.
Project Party is an authority within TCPinpoint, which has a set of permissions defined by role. A Project Party access to tasks and documents relevant to the role they have been assigned, as well as permission to access documents that have been made publicly available to property. Project Party authority is assigned when Project Creators and Project Administrators invite users to a role on a project or in the template builder.
Property Administrator is an authority within TCP that has a set of permissions outside of role-based permissions. A Property Administrator has permission to upload documents to their Property Page, which will be shared across all projects started on that property. Property Administrators can only see projects that they are team members on, even though projects may be started under their property. This authority must be manually set by TCP.
Role refers to the real-world function a TCP user will perform within a given project, such as Retail Design Manager, Asset Manager, Shopfitter, Lease Admin. When a user is invited to a project, the Project Creator or Project Administrator will assign them a role. Roles can also be assigned within the template builder. Users are assigned to tasks in a project based on their role. Role-based permissions are independent of authority permissions.
Role-based permissions refers to the set of permissions afforded to individual team members on a project depending on what role they have been allocated. Every task in a TCP project is assigned to a role, and each role in a project is assigned to a team member. The team member with the role responsible for the task will have permission to view and take action on that task and its associated documents. Role-based permissions are overridden by higher authorities, such as Project Administrator and Project Creator.
A task is a single piece of work in a project, to be completed by users assigned to roles designated in the template builder. Tasks are children, or elements, of phases. Tasks have conditions, which are either yes/no or document upload.
Team Members are users who collaborate on project, invited either directly to the project or added automatically via the template. Team members have role and/or authority based permissions on projects, which determines which resources they can view and take action on.
A template is a repeatable resource that can be used for multiple projects. Templates are created in the template builder, whereby the user will define the workflow, add ledgers, invite team members and define their roles.
A tenant is a person or company who occupies property rented from a landlord.
A TCPinpoint User is anyone who has a TCPinpoint account, typically involved as team members on one or more projects on TCPinpoint. Users are assigned authority on projects by the TCP system, or by Project Creators and Project Administrators. Users are assigned roles on projects by Project Creators. Users are assigned to tasks depending on their assigned role in a project.
A workflow is a sequence of phases and tasks that define the process of a project as it moves from initiation to completion. A workflow is defined in a template and utilised in a project. Workflows are displayed in the 'workflow' tab in the project work space.