TAMU-CC SCLC Scheduler

⏳ Pending Approvals 0

📬 Email Activity

No emails sent yet.

✅ Upcoming Approved Sessions

🗺 SCLC Floor Plan — Daily Room View

Date:

Legend: Booked Conflict Color = course

Hover over rooms for session details. Colors correspond to assigned courses.

＋ New Session Booking

⚠️ Conflict:

Session Details

Session Title *

Booking Type *

Course *

Room / Space(s) *

Hold Ctrl (Windows) or Command (Mac) to select more than one room.

This room is being shared by another course

Date *

Start Time *

End Time *

Requested By *

Your Email *

Facilitator(s) *

Coordinator Notification Email

Repeat / Copy Existing Booking

Is this exact simulation or booking occurring on another date?

Learning Objectives SSH Required

Session Learning Objectives * SSH

Clinical / Research Purpose

Learner Information SSH Required

Actual Simulation Hours Per Student * SSH

Enter the actual number of hours each student participated in simulation activities during this session (e.g. 1.5 for 90 minutes). This is used to calculate total simulation hours for utilization reporting.

Equipment & Simulators Used SSH Required

Other Equipment

SSH Compliance Documentation SSH Required — Research Track

📐 Session Design

Simulation Modality * SSH

Fidelity Level SSH

Debriefing Method SSH

Prebriefing Provided? SSH

🎯 Outcomes & Assessment

Assessment Tool * SSH

Competency Domain SSH

QSEN Competency Alignment SSH

NLN Jeffries Framework Alignment SSH

Outcome Measures / Evaluation Plan SSH

📋 Research Documentation

IRB Protocol # (if applicable)

Grant / Funding Source

Data Collection?

AV Recording?

Additional Notes / Special Instructions

📎 Attachments

Attach Files (simulation scenario, supply list, scripts, etc.)

Max 25MB per file. Files upload when you submit this booking.

✅ Faculty Certification

I certify that the information provided in this booking request is accurate and complete to the best of my knowledge. I acknowledge that this session will be conducted in accordance with TAMU-CC CONHS simulation center policies and SSH accreditation standards. All learners have been or will be informed of simulation policies prior to participation.

📋 Sessions Log

Date	Time	Course	Session	Room	Facilitator	Learners	Sim Hrs/Student	Objectives	SSH Docs	Status	Actions

📈 SSH Compliance Reports

From Semester

Through Semester

Showing: All Time

💡 Pick just "From" for a single semester (e.g. Fall 2026), or set both to cover a range (e.g. Summer 2026 through Fall 2026). Every report below, including tours, uses this same range.

📋

Session Activity Log

Full SSH log with all compliance fields, objectives, learner demographics, equipment — formatted for site visit.

📅

Monthly Utilization

Room-by-room utilization rates, session hours, and peak usage by course.

👥

Learner Participation

SSH breakdown of learners by profession, discipline, training level per session.

🔬

Equipment Usage

Simulator and equipment frequency by session for maintenance and SSH documentation.

📐

SSH Compliance Summary

Complete SSH Research track compliance status with all form fields and documentation gaps.

🎓

Course Activity Report

Session counts, learner hours, and room usage broken down by CONHS course.

🎓 Tours Reports

📊

Tours Summary

Total tours, attendance, group types, and tour frequency by month.

📥

Tours Activity Log

Full tour log with group names, contacts, dates, attendees, areas, and guide assignments.

📅

Tours by Month

Monthly breakdown of tour volume and total attendees for capacity planning.

🧪 Open Lab Reports

📊

Open Lab Utilization

Total requests, approval rates, attendance, student vs. non-student mix, and top courses practiced.

📥

Open Lab Activity Log

Full request log with requester info, student/course info, headcount, practice focus, and status.

⚙ Administrator Settings

☁️ Database Connection (Supabase)

⚠ Not Connected

One-time setup (~5 minutes):

Go to supabase.com → Start for free → sign in with GitHub or email
Click New Project → name it sclc-scheduler → choose a region → set a database password → Create
In your project, click the </> SQL Editor icon in the left sidebar → New query → paste the SQL script below → click Run
Go to Project Settings (gear icon) → API → copy your Project URL and anon public key
Paste both into the fields below and click Connect Database

📋 SQL Setup Script — click to expand, then copy and paste into Supabase SQL Editor

-- Run this once in Supabase SQL Editor
-- Select all text below and paste into Supabase → SQL Editor → New query → Run
-- Safe to re-run: this script is idempotent, so running it again on an
-- existing project will hash any leftover plaintext passwords and tighten
-- the policies below without touching your existing session/tour data.

create table if not exists sclc_sessions (
  id bigint primary key generated always as identity,
  data jsonb not null,
  created_at timestamptz default now()
);
create table if not exists sclc_tours (
  id bigint primary key generated always as identity,
  data jsonb not null,
  created_at timestamptz default now()
);
create table if not exists sclc_users (
  id bigint primary key generated always as identity,
  data jsonb not null,
  created_at timestamptz default now()
);
create table if not exists sclc_settings (
  key text primary key,
  value jsonb not null,
  updated_at timestamptz default now()
);
alter table sclc_sessions enable row level security;
alter table sclc_tours enable row level security;
alter table sclc_users enable row level security;
alter table sclc_settings enable row level security;

drop policy if exists "allow all" on sclc_sessions;
drop policy if exists "allow all" on sclc_tours;
drop policy if exists "allow all" on sclc_settings;
create policy "allow all" on sclc_sessions for all using (true) with check (true);
create policy "allow all" on sclc_tours for all using (true) with check (true);
create policy "allow all" on sclc_settings for all using (true) with check (true);

-- ── Account security: passwords are hashed in the database, never sent to
-- the browser in readable form, and login is verified server-side ──
create extension if not exists pgcrypto;

update sclc_users
set data = jsonb_set(data, '{password}', to_jsonb(crypt(data->>'password', gen_salt('bf'))))
where data ? 'password' and data->>'password' not like '$2%';

create or replace function sclc_hash_user_password()
returns trigger language plpgsql as $$
begin
  if new.data ? 'password' and new.data->>'password' not like '$2%' then
    new.data := jsonb_set(new.data, '{password}', to_jsonb(crypt(new.data->>'password', gen_salt('bf'))));
  end if;
  return new;
end $$;

drop trigger if exists trg_hash_user_password on sclc_users;
create trigger trg_hash_user_password
before insert or update on sclc_users
for each row execute function sclc_hash_user_password();

-- CREATE OR REPLACE cannot change a function's return columns, so drop first
-- (safe: grants and the trigger above are unaffected, this just redefines it).
drop function if exists verify_login(text, text);
create or replace function verify_login(p_username text, p_password text)
returns table(id bigint, username text, role text, name text, email text, must_change_password boolean)
language plpgsql security definer as $$
begin
  return query
  select u.id, u.data->>'username', u.data->>'role', u.data->>'name', u.data->>'email',
         coalesce((u.data->>'mustChangePassword')::boolean, false)
  from sclc_users u
  where u.data->>'username' = p_username
    and u.data->>'password' is not null
    and crypt(p_password, u.data->>'password') = u.data->>'password';
end $$;

grant execute on function verify_login(text, text) to anon, authenticated;

-- Lets a user (or the forced-password-change screen) set a new password
-- themselves without ever exposing other users' password hashes to the browser.
create or replace function change_password(p_username text, p_current_password text, p_new_password text)
returns boolean
language plpgsql security definer as $$
declare
  matched boolean;
begin
  select true into matched
  from sclc_users u
  where u.data->>'username' = p_username
    and u.data->>'password' is not null
    and crypt(p_current_password, u.data->>'password') = u.data->>'password';

  if not matched then
    return false;
  end if;

  update sclc_users
  set data = jsonb_set(
    jsonb_set(data, '{password}', to_jsonb(crypt(p_new_password, gen_salt('bf')))),
    '{mustChangePassword}', 'false'::jsonb
  )
  where data->>'username' = p_username;

  return true;
end $$;

grant execute on function change_password(text, text, text) to anon, authenticated;

drop policy if exists "allow all" on sclc_users;
drop policy if exists "allow reads" on sclc_users;
drop policy if exists "allow inserts" on sclc_users;
drop policy if exists "allow updates" on sclc_users;
drop policy if exists "allow deletes" on sclc_users;
create policy "allow reads" on sclc_users for select using (true);
create policy "allow inserts" on sclc_users for insert with check (true);
create policy "allow updates" on sclc_users for update using (true) with check (true);
create policy "allow deletes" on sclc_users for delete using (true);

-- ── Open Lab Requests: guest/student practice requests submitted without a login ──
create table if not exists sclc_open_lab_requests (
  id bigint primary key generated always as identity,
  data jsonb not null,
  created_at timestamptz default now()
);
alter table sclc_open_lab_requests enable row level security;
drop policy if exists "allow all" on sclc_open_lab_requests;
create policy "allow all" on sclc_open_lab_requests for all using (true) with check (true);

-- ── Attachments: storage bucket for files faculty attach to booking requests ──
insert into storage.buckets (id, name, public)
values ('sclc-attachments', 'sclc-attachments', true)
on conflict (id) do nothing;
drop policy if exists "sclc attachments allow all" on storage.objects;
create policy "sclc attachments allow all" on storage.objects
for all using (bucket_id = 'sclc-attachments') with check (bucket_id = 'sclc-attachments');

💡 Click inside the box above to select all, then copy (Ctrl+C)

Supabase Project URL

Supabase Anon Public Key

Room Names & Types

Email & Center Settings

📬 Email Method ✅ Outlook mailto

Emails are sent directly through your Outlook account. When an email is triggered, a pre-filled draft opens in Outlook — just click Send. No third-party services, no IT approvals needed.

💡 Tip: For the best experience, set Outlook as your default mail app in Windows Settings → Default Apps → Mail.

Default Coordinator Email

Center Name (in emails)

Email Footer

Course Colors

Equipment / Simulator List

👤 User Accounts

🎓 Lab Tours

Share this link with schools and community groups so they can request a tour without needing an account:

Date	Time	Group	Contact	Attendees	Type	Guide	Status	Actions
No tours scheduled

🧪 Open Lab Requests 0

Share this link with students, guests, or outside groups so they can request open lab practice time without needing an account:

Submitted	Name	Email	TAMUCC Student?	Course	Org	# Attending	Practicing	Preferred Date/Time	Notes	Status	Actions
No open lab requests yet