Skip to main content
GullySystem
Wellness

Roles and Permissions for Nutritionists and dietitians

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

Associates see only their own clients, while the head dietitian sees every chart and report. The front desk sees bookings and payments, not lab results. Health data stays restricted by role.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Nutritionists and dietitians

How the business operates.

Clients come for weight loss, PCOS, thyroid, diabetes, pregnancy or sports nutrition, on a one, three or six-month package. The plan changes weekly and each change must be recorded. Most of the work happens between consultations.

Client intake and health history

Keep goals, conditions, food preferences, the diet recall and uploaded lab reports on one profile, open to you and to the associate you assign.

Diet chart builder

Build charts from your own meal templates by condition and preference, then send them out as a branded PDF.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client intake and history. Capture goals, diagnoses, medicines, allergies, food preferences, the twenty-four hour diet recall and uploaded lab reports on one profile. The assigned dietitian and any associate open the same file.
  • Consultation notes. Write each session as a dated note with the complaint, the findings and the changes agreed. Earlier notes stay in order, so the next call starts from what was said last time.
  • Diet chart builder. Assemble a chart from your own meal templates grouped by condition, cuisine and calorie band, then adjust portions for the client. Each revision is saved and the latest goes out as a branded PDF.
  • Food and portion library. Hold the foods, household measures and swaps you use most, with the nutrient values from the source you are licensed to use. Charts pull from this list, so a swap is written once.

Operational bottlenecks to check

Follow-ups are missed

A client stops sending their weight, and two weeks pass. You notice when the client asks for a refund, and by then the chart has been dropped.

Diet charts are rewritten from scratch

Every chart begins on a blank page, although half repeats what you wrote last week for another client with the same TSH report.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and intake

    A new client arrives from a referral, a website form or a message. Goals, conditions, medicines, allergies and food habits are filled in, and a first consultation is booked.

  2. 2. Assessment

    The dietitian records height, weight, waist, blood pressure and the diet recall, and attaches any lab reports. Findings and the agreed goal are written as the first note.

  3. 3. Plan and chart

    A chart is built from saved meal templates and the household measures the client uses. Portions are adjusted, and the finished chart goes out as a PDF.

  4. 4. Follow-up review

    Weight, measurements and meal photos come in each week. The dietitian logs the reading, notes the plateau or the loss and revises the chart when needed.

  5. 5. Follow-up and sessions

    Late check-ins are listed by days of silence. Review calls and clinic visits are booked, and each ends with a note and the next date.

  6. 6. Renewal or closure

    Before the package ends, the client’s progress is shown beside a renewal offer. A client who finishes is closed with a summary of what changed.

Industry reports to connect with

  • Active clients by dietitian, goal and package type
  • Clients overdue for a weekly check-in, by days of silence
  • Weight and waist change by client over the length of the package
  • Charts issued and revised, by dietitian and condition

Questions before implementation.

When should nutritionists and dietitians consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements