09 January 2025

What is Admissions?

Tribal Admissions is a comprehensive system designed to manage the admissions process for educational institutions. It includes key features such as desks, decision making, and offer tracking. The system allows users to perform tasks like making decisions on applications, managing academic reviews, and configuring various admissions settings.

The diagram Admissions overview shows the architecture and the main user personas, which as admissions officers, academic reviewers, applicants, agents, and system administrators and developers.

Admissions overview
Diagram showing the architecture of Tribal Admissions

The user personas are as follows:

Admissions officers

Admissions officers process applications using the Applications app. The main responsibilities of admissions officers are as follows:

  • Process applications: admissions officers are responsible for processing applications at designated desks. Applications officers review submitted applications to ensure all required information and documents are complete.

  • Request academic and credit reviews: admissions officers can request reviews of applications from academic reviewers.

  • Make decisions: admissions officers make decisions on applications, such as offering conditional or unconditional offers.

System administrators assign admissions officers to groups, which are then mapped to roles in Admissions. The roles define the permissions of the admissions officers. For example, the desks where admissions officers process applications, whether admissions officers can publish decisions, and so on. Senior admissions officers can also have permissions to define the settings of features in admissions settings. Admissions officers with the required permissions in admissions settings can also add reference data, such as entry points, programmes, offers, and so on.

Academic reviewers

Academic reviewers are academic staff nominated to review applications and make recommendations on whether to make offers for applications or whether a credit offer is made to the applicant. Academic reviewers use the Academic reviews app as follows:

  • Review applications: academic reviewers assess applications to make recommendations, such as whether an applicant should receive a conditional offer. This involves evaluating the applicant's qualifications, portfolios, or deciding if an audition is necessary.

  • Making recommendations: after reviewing, academic reviewers make recommendations that are used to make decisions on applications. This could involve recommending an offer, a conditional offer, or a rejection.

  • Delegate reviews: If necessary, academic reviewers can delegate the task of choosing reviewers to other academic reviewers.

System administrators assign the groups of academic staff to the role Academic Reviewer or Credit Reviewerwith suitable permissions. Then, add the appropriate staff remit to the reviewers.

Applicants

Applicants can make applications directly and through UCAS or SITS:Vision. When an applicant makes an application and the application has the completion status Received, the applicant is sent an email inviting them to register for the applicant portal. Applicant portal registration enables applicants to register and log in to the applicant portal.

Attention.

The Received status is an important step in the application process, as it signifies that the application is now in the queue for further review and decision making by the admissions officers.

This email contains a link to register an account on the applicant portal. Applicants can then log in to the applicant portal to:

  • Edit personal information: applicants can edit their personal details, contact information, emergency contacts, and preferred communication language.

  • Manage their applications: applicants can respond to offers directly through the portal. If enabled in admissions settings, applicants can request deferrals or withdrawals of their applications.

  • Upload documents: applicants can upload documents related to their applications, such as copies of passports and other required documentation.

Agents

Agents working in agencies use the agent portal to progress applications on the behalf of applicants. For example, agents can upload documents related to applications, such as copies of passports and other required documentation.

Agents get an invite to the agent portal when the agent is created in Admissions. System administrators can set the permissions on agents to determine the functionality available to agents in the agent portal.

System administrators and developers

System administrators use System admin to manage the authorisation of users in Admissions. System administrators also set up and manage integrations of Admissions with UCAS. System administrators can use workflows to automate the progress of applications through the admissions process.

Developers can integrate third-party systems with Admissions using the integration APIs. Streams enable applications to receive events from Tribal modules, such as Admissions and SITS:Vision. Power Automate enables developers to automate flows between Admissions, SITS:Vision, and other systems.

SITS:Vision and third-party applications integrate with Admissions through the integration APIs, which are documented on the API catalogue. UCAS integrates with Admissions through the UCAS XML-Link.