Requesting Access

Deceema access connects you to high-performance computing resources, project storage, and digital services. A complete request helps the Deceema team place you in the correct project and assign the Quality of Service (QoS) options your work requires.

This guide explains what to prepare, how to submit a strong request, and what to check when access is approved.

Before You Request Access

Gather the following information before starting your request:

• Your identity: Full name, institutional email address, organization, and department or research group.
• Project details: Project name, a concise description of the work, and the project code if you are joining an existing Deceema project.
• Project owner or sponsor: The principal investigator, project lead, or other person responsible for approving your participation.
• Technical requirements: The applications, compute resources, GPUs, storage, or hosted environments you expect to use.
• Time frame: The expected start date and duration of the work.
• Collaborators: Other people who need access to the same project and data.

Ask the project owner first

If you are joining an existing project, confirm its exact project code and owner before submitting your request. This prevents access from being assigned to the wrong allocation.

Choose the Right Request Path

Your request will normally fall into one of these categories:

Request	Use it when
Join an existing project	A Deceema project and project code already exist, and you need to be added as a member.
Create a new project	The work does not belong to an existing allocation and needs its own project, resources, and ownership.
Change existing access	You already have an account but need a different project, QoS, storage allocation, or service.

Use your organization's approved Deceema access channel to submit the request. If you are unsure which path applies, contact Support before submitting.

Write a Request That Can Be Approved

A useful project description is specific enough for the Deceema team to understand the work and assign appropriate access. Include:

1. The goal — what the project is trying to achieve.
2. The workload — simulations, data processing, machine learning, application hosting, or another type of work.
3. The scale — expected task count, GPU requirements, run duration, data volume, or concurrency where known.
4. The software — key applications, libraries, containers, or environments.
5. The data — where it comes from, how much is expected, and any handling requirements.
6. The people — project owner, team members, and external collaborators.

Example project description

Objective: Analyze a research dataset using a reproducible computational workflow.

Workload: A combination of data preparation and scheduled compute jobs.

Requirements: Access to the relevant project allocation, project storage, required software, and the QoS appropriate for the workload.

Team: The project owner and named collaborators who will work with the data and results.

Replace this example with concrete information about your own project.

What Happens Next

• 1. Request

  You provide your identity, project, sponsor, and technical requirements.

• 2. Review

  The request is checked for completeness and the required project approval.

• 3. Provisioning

  Your account is associated with the approved project and available QoS options.

• 4. Activation

  Follow the instructions you receive to activate the account and complete your first sign-in.

The time required depends on the completeness of the request, project-owner approval, and the resources or services being requested.

Validate Your Access

After activation, review your provisioning confirmation or account details in Deceema Admin. Confirm that they include:

• The project or projects you expect to use.
• The correct project codes.
• The QoS options associated with those projects.

You will use the project code as the Slurm --account value and the relevant QoS as the --qos value in job scripts.

Something is missing?

Do not guess a project code or QoS. If your account details do not match the access that was approved, contact Support and include the affected project code and a description of what you expected.

When the account details are correct, continue to Getting Started to prepare your first job.

Avoid Common Delays

Requests often need clarification when they contain:

• A personal email address instead of an identifiable institutional account.
• A project name without the exact project code.
• No project owner or sponsor for an existing allocation.
• A broad description such as “HPC access” without a workload or objective.
• Resource requests that do not explain the need for GPUs, storage, or other specialized services.
• Multiple collaborators whose roles or access needs are unclear.

Review these points before submission to reduce follow-up questions.

Keep Your Account Secure

Your Deceema account is personal to you.

• Never share your password, authentication code, or active session.
• Use only the projects and data you are authorized to access.
• Keep contact and project-membership information current.
• Report suspected credential exposure or unexpected access immediately.
• Ask for access to be changed or removed when your role in a project ends.

Access Checklist

• I have an identifiable institutional email address.
• I know whether I am joining an existing project or creating a new one.
• I have the correct project code and project-owner details where required.
• I described the workload, software, data, and expected resources.
• I named the collaborators who need access.
• After activation, I verified my projects and QoS options against my approved account details.