TCPinpoint Knowledgebase and Documentation
Getting Started with TCPinpoint
First things first: build a template with a custom workflow, and invite team members to collaborate. Then, start multiple projects using that template, and then watch the waterfall at work. Upload and retreive documents, leave comments for your team and track the progress of your projects.
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.
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.
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.
A tenant is a person or company who occupies property rented from a landlord.
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.
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.
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.
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.
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.
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.