Services
LABIS
Lab Intelligence System
A lab management system that supports many labs — choose a lab to build its homepage and run ERP work such as people, projects, purchasing, equipment and outputs, plus LIMS.
What it does
LABIS (Lab Intelligence System) is a lab management system that supports many labs. A department runs several labs side by side, and each lab's data is kept separate. While the analysis services handle data, the things that actually keep a lab running — who is here, which project they are on, what was bought, which instrument is due for a check — usually live in scattered spreadsheets. LABIS gathers them in one place, lab by lab.
Once you choose a lab, you use two sets of features in it.
| Set | What it does |
|---|---|
| Building the lab homepage | Builds a public homepage that introduces the lab — masthead, text, hero image and logos, sub-pages, member list, publication list, a public short address, and connecting the lab's own domain |
| Lab-management ERP work | Handles the lab's day-to-day operations — members-only notices, work status, projects, weekly reports and performance reviews, people, leave, roster and lab operations, purchasing, instruments and inventory, outputs, LIMS (samples and experiments), and Google Sheets linking |
The homepage is a public screen that anyone can see; the ERP screens are used only by signed-in members assigned to that lab. The department can have at most 5 labs that are not closed (dormant labs count).
Building the lab homepage
Each lab has one homepage. Lab operators (lab manager, PI) and the department admin write its content in
the 홈 페이지 (Home page) section of 관리자 설정 (admin settings). No lab's content is built into
the program; only what the lab itself writes is shown.
Who sees what
A homepage address is the LABIS address followed by ?lab=<short address> (for example
?lab=SYSMED). A lab without a short address opens with ?lab=<lab number>.
| Visitor | Screen that opens |
|---|---|
| Visitor who is not signed in | The public homepage — Home · Members (only for labs that made the list public) · sub-pages switched on as menus · Publications (when there is a list). No management data; sign-in and the lab list are at the top |
| Signed-in member of that lab | Enters the app, where Home is the default screen. Uses both the homepage screens and the ERP screens |
| Signed in but not a member | The public homepage with a "not a member" notice |
| Someone who just signed out | The entry screen (sign-in and lab choice) |
- The address of a lab that does not exist or has been closed shows a single sentence, "The lab could not be found or is no longer in operation"
- When your sign-in expires, the public homepage appears with a
로그인(sign in) button. It does not redirect you automatically, so sign in again - Notices are not part of the homepage. They are a board only members see (see "Lab-management ERP work" below)
What you write on the homepage
In 관리자 설정 › 홈 페이지, fill in the items below and press 홈 페이지 저장 (save home page) (the public address is saved separately — see below the table).
What you write is both the app's first screen (Home) and the public homepage, so do not put internal
information in it.
| Item | Content |
|---|---|
| Masthead title | The top line, title and bottom line of the masthead (one line of up to 120 characters each). Empty fields take the default — on the public homepage the top line is "Lab Intelligence System", the title is the lab name and the bottom line is "연구실 홈페이지" (lab homepage) (inside the app the top line is the lab name, the title is LABIS and the bottom line is the LABIS description). If you enter a title, the browser tab title follows it |
| Title and body | The welcome text. Separate paragraphs with a blank line and put links inside a paragraph as [text](address). HTML cannot be used; text appears exactly as typed |
| Hero image and hero image link | An https:// address or an uploaded file (PNG, JPEG, WebP, GIF, 512 KiB per image). If you add a link, clicking the image goes there. There is an option to invert the colours of a line drawing in dark mode |
| Link buttons | One per line, up to 12. Separate the name and the address with a vertical bar |
| Logos and logo group title | Logos of related institutions. If the group title is empty it reads "관련 기관" (related institutions) |
| Bottom line | A short line at the very bottom of Home (for example Since 2010) |
| Sub-pages | Separate pages opened by links from Home (below) |
| Make member list public | When on, the Members tab is shown even to people who are not signed in |
| Publications | A Google Scholar snapshot (below) |
Link addresses are accepted only as https:// or an in-app path (#/…, /labis/…). If an image or link rule is
broken, the whole save is refused, so read the refusal message. Images and text together must stay
within 3 MiB. A saved change takes up to about a minute to appear on the public homepage.
The public address is entered in its own field at the top of the same section and saved with
공개 주소 저장 (save public address) — 홈 페이지 저장 does not save it. The short address (for example
SYSMED) is 2–32 letters, digits and hyphens starting with a letter; it cannot end in a hyphen, and reserved
words such as api, admin and login are not allowed. Case is ignored, and it is refused if another lab
already uses it. Saving it empty removes it and the lab goes back to its number address. After a change the old
short address closes within a minute, while the number address keeps working.
Sub-pages and menu tabs
Pages opened separately from Home, such as recruiting notices or research-area introductions, are
made as sub-pages (up to 12 per lab). The address looks like #/p/<name> and is the same inside
the app and on the public homepage. So a link written in the body such as
[Position Opening](#/p/positions) works in both. The name uses lowercase English letters, digits
and hyphens, and cannot repeat.
A sub-page comes in two forms.
- Card page — an introduction and cards (up to 12 cards, up to 20 items per card). In the card
field, write a
## Card titleline followed by- itemlines - Research-area page — a single research-introduction page made of an opening introduction and cards per research area (up to 12 areas). Each area can carry tags and representative papers, and the per-area paper counts, year range and the area × year dot map are counted by the screen itself from the papers you entered. In the settings screen, choose the form "research-area page" and paste in the content. Broken content is stopped before saving
Turning on 메뉴에 표시 (show in menu) for a sub-page makes it a tab (in both the app and the
public homepage). The tab name can be set separately and falls back to the page title if empty. You can
choose which menu page the Publications tab comes after.
Members and publications
- Members — only three columns are shown: name, position and team. Contact details and email are
not shown. The list comes from the people-roster sheet (when the lab's sheet is linked to that
document), otherwise from active accounts. Members see it regardless of the public setting; people who
are not signed in see it only for labs that turned on
멤버 명단 공개(make member list public). A photo can be uploaded on a member card — operators can upload or delete anyone's photo, while a member uploads only their own. A photo uploaded by an administrator or brought in from the lab homepage (artifact) cannot be changed by the member. The picture is cropped to a centred square, and without a photo the first letter of the name appears in a circle. If a name changes on the roster, that person's photo must be uploaded again to show - Publications — paste a snapshot made from Google Scholar into the field on the settings screen,
press
가져오기(import), then press홈 페이지 저장(save home page). If you save without pressing가져오기, the pasted content is not applied and is dropped. It does not pull live, so when things change, repeat the same order (paste →가져오기→홈 페이지 저장). It carries total citations, h-index and i10-index, the paper list, and Scholar, ORCID and PubMed links, and the screen lets you view it newest first, by citations, or by search (up to 1000 papers). It is separate from the paper table under성과(Outputs)
Connecting the lab's own domain
Visitors who arrive through a domain the lab owns (for example lab.example.ac.kr) can be sent on to
this lab's public homepage. In 관리자 설정 › 주소 포워딩 (address forwarding), add the domain and choose
the screen to send to (Home, or a sub-page, Members or Publications). Up to 5 per lab.
- When you add a domain, the name and value for ownership verification appear
- The domain's owner puts that TXT record in DNS and makes the domain point to the LABIS server
- Press
DNS 확인(check DNS). Both must match for it to become확인됨(verified) - Only verified domains are forwarded. A domain that is unverified or failed is treated exactly like an unknown name
| Status | Meaning |
|---|---|
| 확인됨 (verified) | Ownership is confirmed and the domain is forwarded |
| 소유 확인 대기 (awaiting ownership check) | Added but not checked yet |
| 확인 실패 (check failed) | The reason is shown with it — no DNS record, points to another server, timeout, TXT missing, TXT value differs |
| 다른 연구실이 소유 확인함 (another lab verified it) | The lab that verified first is the owner. One domain belongs to one lab |
| 예약된 이름 (reserved name) | A name the service uses, so it is not verified or forwarded. You can still remove it from the list |
- Registering first does not make you the owner. The lab that verified ownership is the owner
- If a re-check fails, the verification is dropped. There is no automatic re-check, so press it again yourself after changing DNS
- After you change the target screen or remove a domain, it takes up to about 2 minutes to reach visitors
- This screen covers the lab's side. The certificate and web-server connection are set up separately, once per domain, by the server administrator. Once the domain shows verified, tell the server administrator its name
Lab-management ERP work
These are the screens for running the lab. They open only to signed-in members assigned to that lab, and what you see depends on your permissions (see "Permissions at a glance").
| Group | What it does |
|---|---|
| Notices (공지) | A board only members see. Not shown on the public homepage |
| 업무현황 (work status) | Cards for projects, people, purchasing, grant status, assets and outputs show how many items need attention, and 업무 바로가기 (shortcuts) has buttons to the screens you use most. Cards and buttons you have no permission for are hidden |
| Grant status (과제현황) | Takes the grants in the research-records sheet and sorts them into active, upcoming and ended by participation period and today's date |
| Projects | Internal research units, separate from funded grants — one team lead and assigned members, progress (0–100%), status, weekly report lookup |
| Weekly reports | Members submit report files every week, and team leads and administrators review them in two stages |
| People | People & leave (leave requests and approval), roster, performance reviews, lab operations |
| Purchasing | An approval chain from request → team-lead approval → PI approval → purchase by the purchasing team → inspection, and repurchase |
| Assets | Instruments and their check schedule, reagent and consumable stock with stock in/out |
| Outputs | Papers, patents, technology transfers |
| LIMS | Sample intake and storage, experiment records |
| Google Sheets linking | Links a Google Sheet to each item for import and export |
- Lab operations reads the lab's Google Sheet and shows it. Choose a year (2023–2026) to see that year's sheet; sheets exist for 2025 and 2026. The roster shows the current roster regardless of year
- The payroll table shows the same sheet's monthly labor costs per person and per project, and opens only to lab operators and above. Amounts may include scheduled payments, so they are not amounts already paid. Together with the funding screens (funding status, funding) it is not yet open as a menu
- Notices — any member can read them; lab managers and above post them. Title up to 200 characters, body up to 10000 characters (line breaks are kept). Pinned notices come first and the rest are most recent first. They are not locked by menu permissions
- ERP covers the lab's operational records. Payroll settlement, double-entry bookkeeping and tax filing are not included
What to know before you start
You enter with your contextBio account. LABIS has no sign-up or password screen of its own. Profile and password are managed on the contextBio account screen.
The homepage can be viewed without signing in, while ERP requires an invitation. To enter the work screens of an existing lab, a lab operator (PI or lab manager) must assign you by email in the admin settings. An account that has not been assigned cannot enter that lab.
Members see little at first. Home, Members, menu pages, Publications and Notices, 업무현황 (work status), weekly report submission, Projects and Purchasing are open from the start (work status shows only the cards for groups opened to you); the other work groups (grant status, people, assets, outputs, LIMS) appear only once the PI opens them. A missing menu is a permission, not a fault (see "Permissions at a glance").
The screen is in Korean. Menu names below are given in English with the Korean label where it helps.
The funding screens are not ready yet. The entry screen lists them, but they do not appear in the menu.
Getting in
- Open LABIS with the
Open LABISbutton above this page. If sign-in is needed you go to the contextBio sign-in screen and come back - Choose a lab — pick a lab from the list and press
LABIS 입장(Enter LABIS). If you have entered a lab before, or you belong to only one, you go straight in without this screen. On the entry screen,연구실 홈페이지 보기(view lab homepage) opens that lab's public homepage without sign-in - Home — the first screen a member sees on entering. From there the tabs at the top move between the
homepage screens (Members, menu pages, Publications), while the members-only screens (Notices, and the
ERP work screens starting from
업무현황) are reached through theERPtab at the end of the main tab row (right after the home menu tabs) - Once you are in, the lab's short address (or its number if it has none) is written in the address bar. Reloading or sharing the address opens the same lab
- If you belong to several labs, switch in the
연구실 · 연도(lab · year) section of My page (마이페이지, opened by clicking your name in the masthead). Every record you see belongs to the lab currently selected
You can also open a new lab yourself. Enter a name (and room) under + 새 연구실 개설
(open a new lab) on the entry screen; the lab is created and its creator becomes its PI. The
department can have at most 5 labs that are not closed (dormant labs count).
The screen
There are two rows of tabs. The main tab row under the masthead holds the same tabs as the public
homepage (Home · Members · pages switched on as menus · Publications), followed at its end (right after the
home menu tabs) by one ERP tab. The work screens are not on the main tab row. Entering through the
ERP tab lights that tab while an ERP screen is open and adds a secondary tab row under the main one,
where you pick a work screen. The masthead has no ERP entry. The screens fall into two groups.
- Homepage screens — Home · Members · sub-pages switched on as menus · Publications. These have the same content as the lab homepage and are not locked by menu permissions
- Members-only (ERP work) screens — enter through
ERPand pick one in the secondary tab row. The tabs stand in this order: 업무현황 (work status) · Projects · Weekly reports · Notices · Grant status · People & leave · Roster · Performance reviews · Lab operations · Purchasing · Instruments · Inventory · Outputs · Samples · Experiments, and screens locked by permission are left out. Notices, work status and weekly report submission are open to every member; for the rest you see only the screens opened to you. Notices are never locked by menu permission, so every member sees theERPtab; pressing it opens the first screen you can see (usually work status). Each screen keeps its address, so old bookmarks still open. These screens exist only in the app for signed-in members, not on the public homepage or the entry screen
My page (마이페이지) opens when you click your name in the masthead. It holds your account (name,
email, position, role), 연구실 · 연도 (lab · year), 다른 앱으로 이동 (go to other apps), the labs you
belong to, your member photo (uploaded under the same rules as on the Members tab) and shortcuts (weekly
report submission · Notices · ERP); administrators (lab manager, PI, department admin) also get an
앱 관리자 설정 (app admin settings) card.
관리자 설정 (admin settings) is a separate screen that gathers the lab's settings, apart from these
two groups. It is not on either tab row; open it from the 앱 관리자 설정 card on My page.
The menu layout and order may change as the screens are reworked, so this document refers to screens by name.
Switching labs, choosing the year and moving to other apps are not in the masthead but in the
연구실 · 연도 (lab · year) and 다른 앱으로 이동 (go to other apps) sections of My page (every
member). The same 연구실 · 연도 section is also in admin settings. The year (2023–2026) applies to
screens that read a sheet per year, such as lab operations (the roster is the current roster, independent
of year), and is remembered by the browser. The year note at the top of such a screen links to My page. If
the sheet for a year does not exist, it
shows "no data".
Everyday tasks
Submitting a weekly report — in 주간보고 (weekly reports), choose the report week (it snaps to
that week's Monday) and a project, drop in your files and press 제출 (submit). Who submitted and when
are recorded automatically.
- Every member must submit every week, and the screen is open to all members regardless of permission settings. The deadline is 23:59 on that week's Sunday
- A report covers this week's key progress · next week's plan · items for discussion ("none" if there are none)
- Use the
주간보고_양식.pptxtemplate linked on the screen. Put your name and the report week in the file name (for example홍길동_2026-09-21_주간보고.pdf) - Only documents, images and archives are accepted — 30 MB per file, 10 files at a time, 100 MB in total
- If the lab has a submission folder set, files gather in the lab's shared-drive
WeeklyReportfolder, in a folder per week (Monday). A lab without a folder set keeps them in server storage - Uploading again for the same week keeps the earlier file too. Delete a wrong upload from
내가 제출한 보고서(reports I submitted) - Read approved review comments under
받은 검토의견(review comments received)
Reviewing weekly reports (team leads and administrators) — see the week's submission status (submitted, late, not submitted, before deadline) and review in two stages. Everyone who is currently employed in the lab except the PI is a submission target.
- Stage 1 — team lead. A team lead sees only their own members' reports. Write a team-lead comment and
either
1차 승인(approve at stage 1) or반려 요청(request rejection) (입력 완료(done entering) only saves the comment). A rejection needs a reason, and when the report is submitted again it returns to the stage-1 queue. Authors without a team lead skip stage 1 - Stage 2 — final administrator (lab manager or above). Only reports that passed stage 1 can be
approved. A draft of the review comment is already filled in, so edit it and then press
승인 완료(approve) (입력 완료only saves the comment). Once approved it is locked, and the team-lead comment and review comment are sent to the author by mail and Slack. You can also전체 승인(approve all) everything that passed stage 1 in one go
The review-comment draft is written automatically right after submission. The default is the lab's
local language model (Qwen), and the final administrator can switch the draft model to Claude. Qwen does not read PDFs or images at
all — not even a PDF that contains text — so a report submitted only as a .pdf, like the example above,
gives Qwen nothing to read and gets a rule-based draft. For PDFs and images to be read into the draft, the
final administrator must choose Claude. A rule-based draft is also used when the model is unavailable, and
in either case the reason is shown. The draft is a starting point; what the administrator edits is
final.
Requesting leave — + 휴가 신청 in People & leave. Enter the type (annual, sick, official,
other), dates, number of days and reason. A lab operator changes the status to approved or
rejected (승인·반려). The number awaiting approval shows on the People card of the work status screen.
Requesting a purchase — + 구매 신청 in Purchasing. Enter the item, project, vendor, quantity,
unit price and requested amount. The request moves through member request → team-lead approval
→ PI approval → purchase by the purchasing team → inspection; open a row to see its current stage,
its history and the dates recorded automatically at each step. Rejection, inspection rejection
and cancellation require a reason. Pressing 재구매 (repurchase) on an earlier row pre-fills the item,
vendor, unit price and so on, but it is a new request that goes through approval from the start. Filter
the list by search, type, approval stage and grant funding, and pick the visible columns with the layout
and column controls (표 구성·열 표시). Members can see the full list, but can edit only the requests they made themselves.
Managing a project — click a name in the Projects list to see its team, progress and weekly report lookup. The project's team lead and the lab operators update progress and assign members here. A project has one team lead and may have several members; only lab operators choose the team lead.
Performance reviews — in Performance reviews, team leads review their members and the director reviews project team leads. For each month and project, score achievement, collaboration and responsibility from 1 to 5 and note strengths and areas to improve. You cannot review yourself, and a submitted review cannot be edited, so save a draft first. A draft is visible only to its author; a submitted review is visible to the reviewer, the person reviewed and the director. The PI (or department admin) designates the director.
Registering outputs, samples, experiments, instruments and stock — use the + 등록 (register) button
at the top of each screen. Inventory can be filtered to low or expired stock (부족·만료만 보기), and instruments whose check
is due are counted on the Assets card of the work status screen.
Working with tables — click a column header to sort. If you have permission, a row's status can be changed in place.
What administrators do
These live under 관리자 설정 (admin settings), opened from the 앱 관리자 설정 (app admin settings)
card on My page (click your name in the masthead). Which sections you see depends on your role.
- Lab · year — the same as on My page. Switch labs and choose the year (
다른 앱으로 이동, go to other apps, is only on My page) - Members (
팀원) — enter emails, one per line, choose a role and press배정(assign). An address that already has a contextBio account is assigned immediately; otherwise an invitation link is created. Copy it from pending invitations (대기 중인 초대) with링크 복사(copy link) and pass it on yourself — LABIS does not email invitations - Card-level access for the dashboard (PI) — for each member, set the grant status, projects, people,
purchasing, assets, outputs and LIMS cards to none, view or edit (
불가·보기·편집). Changes apply once you press변경사항 저장(save changes) - Admin review — handle each week's submission status, review comments and approvals in
주간보고 검토(weekly report review) (see "Everyday tasks" above). The older보고서 검토(report review) screen covers per-project text reports and team leads' monthly and quarterly reports - Home page and address forwarding (lab manager and above) — the lab homepage content, the public short address and connecting the lab's own domain (see "Building the lab homepage" above)
- Google Sheets link — enter a sheet address per item and it is read and applied as soon as you save (see "Working alongside spreadsheets")
- Labs (
연구실, department admin) — add and close labs. A lab no longer in use is not deleted but closed — its records stay, and a closed lab does not count toward the limit of 5
Permissions at a glance
There are three roles — member, lab manager and PI — plus a department admin who sees the whole department. Lab managers and PIs together are called "lab operators".
| Action | Member | Lab manager | PI |
|---|---|---|---|
| View Home, Members, menu pages, Publications and Notices · work status · submit weekly reports · view projects · view and request purchases | ✓ | ✓ | ✓ |
| View and edit grant status, people, assets, outputs, LIMS | as opened | edit by default | always edit |
| Register papers, patents, samples, experiments | if the menu is open | ✓ | ✓ |
| Register projects, instruments, technology transfers · approve leave · apply the roster to accounts | ✓ | ✓ | |
| Edit the homepage · post notices · address forwarding · assign members (member, lab manager) · final weekly report review · link Google Sheets | ✓ | ✓ | |
| Assign PIs · change roles · remove members · delete grants · adjust card-level access | ✓ |
- Permissions never exceed the role. Giving a member edit (
편집) does not unlock actions reserved for lab managers and above (the bottom three rows of the table) - A member can see the full purchase list, but can edit only the requests they made themselves
- PIs and department admins are not subject to adjustment — they always have full edit
- A department admin can do everything in every lab
Working alongside spreadsheets
You do not have to abandon the Google Sheets you already use. LABIS supports both sheet → LABIS import and LABIS → sheet export.
- Row 1 of a sheet is the header. Use the column names listed under the sheet template in the admin settings; order does not matter
- For a file with several worksheets, paste the address including
#gid=, or name the tab the same as the item - People are matched by their name on the roster. A row whose name differs from the roster is not applied
- Import does not replace everything. Of the rows that disappear from the sheet, only those that came from the sheet are removed; rows entered on screen stay. Grant status is more cautious still — rows missing from the sheet are only marked, never deleted
- If the server administrator has turned on periodic collection, linked sheets are re-read at a set
interval, and nothing is touched if the content has not changed. To apply changes at once, an
administrator presses
연결된 항목 전부 가져오기(import all linked items) - The lab operations screen re-reads its sheet every 30 seconds while it is open. Editing a row and saving (lab operators and above, with edit permission on that menu) writes straight back to the original Google Sheet. If the original changed in the meantime, it does not save and tells you. Cells with formulas, merges or validation rules must be edited in the original sheet. The roster cannot be edited on screen; edit it in the original sheet
- The Google Sheet is also used for the lab homepage's member list. If the roster sheet is linked, the name, position and team are taken from it
Where people get stuck
The screen's messages are in Korean; the quotations below are translations.
"This account has not been invited to LABIS yet." Ask a lab operator of that lab for an invitation. If you received an invitation link, open that link first.
A menu or work status card is missing. Work menus are not on the main tab row — enter through the
ERP tab at the end of the main tab row (right after the home menu tabs) and look in the secondary tab row. Admin settings and lab
switching are not on a tab row either but on My page (your name). If it is not in the secondary tab row
either, that area is locked to none (불가). Members start at none
(except Projects and Purchasing). Ask the PI to open it. Typing the address directly just brings you
back to Home.
There is no + 등록 (register) button. The menu is open to you for viewing only, or the action is
reserved for lab managers and above.
"Could not load (…)". Pass the code in brackets to an administrator as it is. On grant status it is usually a sheet-permission problem — the list below it is then the last saved content.
I edited the sheet but LABIS did not pick it up. Check the header and tab names, and that
people's names match the roster. If it is urgent, an administrator can apply it at once with
연결된 항목 전부 가져오기 (import all linked items).
The lab list does not load. If you see "could not load the list — enter anyway", press
LABIS 입장 without choosing a lab. You go into a lab you belong to.
A new lab cannot be created. The name is taken, or 5 labs that are not closed (dormant included) already exist. Ask the department admin to close a lab that is no longer used.
Saving the homepage is refused. An image size (512 KiB per image, 3 MiB in total) or the link format
(https:// or an in-app path #/… or /labis/…) was broken. Read the refusal message and fix it. Nothing is saved in part; the
whole save is refused.
I edited the homepage but the public screen does not show it. The public screen can lag by up to about a minute. If it stays the same, reload.
The public homepage has no Members tab. 멤버 명단 공개 (make member list public) is not turned on.
If there is no Publications tab, the publication list is empty.
The public short address will not save. A character rule was broken, it is a reserved word, or another lab already uses it. Check the hint under the input.
A domain shows 확인 실패 (check failed). Look at the reason beside the status. Usually DNS has not
propagated yet or the TXT value differs. Fix it and press DNS 확인 again. If it shows "another lab
verified it", the lab that verified first uses that domain.
I approved a weekly report but no notice went out. If it shows "notice channel not configured — waiting", mail or Slack is not set up on the server. The approval is saved, so resend after the connection is set up (see "Software availability" below).
A performance review cannot be edited. Submitted reviews are final.
Software availability
LABIS runs no computation programs. Instead it relies on outside services for sign-in, spreadsheets, mail and Slack, and language models. If one of them is not connected, only that feature stops.
What it uses
| What | Used for | When missing or disconnected |
|---|---|---|
| contextBio account | Sign-in — every work screen | You cannot enter; you are sent back to sign-in. The public homepage opens without sign-in |
| Google Sheets (service account) | Per-item sheet import and export, grant status, roster, lab operations | Admin settings shows "no service account". Only import from sheets shared with "anyone with the link" works; export and editing the original sheet do not |
| Google Sheets (per-sheet sharing) | As above | A sheet not shared with the service account shows "no permission to read the sheet", and the screen shows the last saved content. Editing the original saves only if it is shared as editor |
| Google Drive | Reading the list of spreadsheets in a Drive folder; the lab's shared folder (WeeklyReport) where weekly report files gather |
An error message appears under the folder address. The folder must be shared with the service account as viewer. If the submission folder is cut off, weekly report submission is refused with an error message and nothing is quietly saved to the server's disk |
| Mail (SMTP) and Slack | Notices of weekly report approval or rejection — sent to the person's own mail address and to Slack (a direct message, or a webhook to the lab's channel) | Weekly report review shows "notice channel not configured". The approval is saved and the notice waits; resend after setup |
| Local language model (Qwen) and Claude | Drafting weekly report review comments. The default is the lab's local Qwen; the final administrator can switch to Claude | "(not configured)" is added to the model list, and a rule-based draft is used instead. The reason is shown beside the draft |
| Email sending service | Sending individual reviews from the older 보고서 검토 screen |
Reviews are kept in the send queue. "Accepted for delivery" does not mean the recipient has read it |
| DNS and web server | Forwarding the lab's own domain — ownership check (DNS), certificate and web-server connection | The domain shows 확인 실패, or even after it is verified it is not forwarded until the server administrator connects it |
The service account's email address is shown in the Google Sheets section of the admin settings. Share sheets and folders with that address.
What to do when blocked
Connections are not something you can set up. The service account, mail and Slack, language models and domain connection are configured on the server by an administrator.
- Note the message exactly as shown — the code after "could not load", the authentication line in admin settings, the error under the Drive folder, the notice status in weekly report review, the failure reason beside a domain
- For a sheet-permission problem the sheet owner can act first — share with the service account address shown, as viewer if reading is enough, as editor if you want to edit from LABIS
- If that does not help, send an administrator the message together with the lab name and which screen (item) it was
References
13 items
The open-source software and outside services LABIS is built on. It calls no scientific computation programs, so there is nothing here to cite in a paper — this list simply states what the service stands on.
Web and data layer
- Next.js — Vercel. Next.js. nextjs.org
- React — Meta Open Source. React. react.dev
- TypeScript — Microsoft. TypeScript. typescriptlang.org
- Prisma ORM — Prisma. Prisma ORM. prisma.io
- PostgreSQL — PostgreSQL Global Development Group. PostgreSQL. postgresql.org
- Tailwind CSS — Tailwind Labs. Tailwind CSS. tailwindcss.com
Authentication, spreadsheets, integration and testing
- Auth.js (NextAuth.js) — Auth.js (NextAuth.js). authjs.dev
- SheetJS — SheetJS. SheetJS Community Edition. sheetjs.com
- Google Sheets API · Google Drive API — Google. developers.google.com/sheets · developers.google.com/drive
- Nodemailer — Nodemailer. Nodemailer. nodemailer.com
- Ollama · Qwen — The lab's local language model (weekly report review drafts). Ollama. ollama.com · Qwen. qwenlm.github.io
- Claude API — Anthropic. Claude. anthropic.com (weekly report review drafts — optional)
- Playwright — Microsoft. Playwright. playwright.dev
Last updated ·
Docs