DM Redline staff manual
Everything Diverse Media needs to run a client review: setting a project up, putting Redline on a site, working the comments, and keeping the server healthy. What the client sees is in the client guide, which is worth reading once so you know what you are asking them to do.
How Redline is put together
There are three pieces. Knowing which one is misbehaving saves most of the time you would otherwise spend guessing.
| Piece | Where it lives | What it does |
|---|---|---|
| The server | redline.diversemedia.sg | Holds projects, accounts, comments, screenshots and recordings. This admin, the client sign-in page, the account page and the images/PDF viewer are all served from here. There is no database: everything is JSON files under data/. |
| The review layer | One line in the client site’s <head> | review.js draws the bar, the pins and the panel over the site, takes the screenshots, and talks to the server. It loads first so it can hold the page’s clock, which is what makes Freeze and Moments possible. |
| The guard | _redline/guard.php in the site’s own folder | Optional. Stands in front of a staging site so that only people with a Redline account for that project can open it — pages, images, 3D models and all. |
A site can use the review layer alone (a public site), the guard alone (rare), or both, which is the usual arrangement for a private preview.
Finding your way around admin
The admin has four places along the top — Projects, Board, People and Settings — and everything to do with you sits under your own name at the right.
| Where | What is in it |
|---|---|
| Your name, top right | Click it. My account (your password and which emails you get), Staff manual (this page), Client guide, and Sign out. A long name is shortened on the button; the menu always shows it in full, so you can be sure whose account you are signed in to. |
| A project card | Four controls, in the order you use them: Board, Edit, Images & PDFs, and More ⌄. |
| More ⌄ on a project card | People on this project (tick or untick who reviews it, or paste new emails), Activity (who has visited, when and for how long), Export comments (CSV), Developer notes (text), Copy install line, and Import comments…. These are the things you need now and then, so they are kept out of the way rather than crowding the card. |
The same idea runs through the whole system: the one or two things you do most are buttons, and the rest sit behind a ⋯ or a More. Anything that downloads a file is behind an Export button with the same two choices everywhere — a spreadsheet for people, developer notes for whoever builds.
Starting a project, end to end
The whole sequence, in the order you actually do it. Each step is explained in detail further down.
- Projects → New project. Name it the way the client would say it (“CWM Jubilee”, not “cwm-j-v2”). The short name is used in links and in the install line, and cannot be changed later.
- Enter the site address, then check Addresses allowed. The address you typed is added for you. Add any other address the site will answer on, one per line. Nothing else is accepted.
- Set the starting password for this project. Press Make one and keep it. This is the password every client on this project is given to begin with, and it is theirs to change afterwards.
- Choose who can open the site. For a staging site, that is Redline accounts only.
- Set the feedback due date, and decide whether the project closes itself to clients after it.
- Check the switches: clients seeing each other’s comments, screenshots, recordings, guests, and the first-time/returning question.
- Tick who gets the emails under “Email new comments to”. Yourself at least.
- Save, then install Redline on the site (see below) and upload it.
- Add the client’s people: on the project card, More ⌄ → People on this project. Tick anyone who already has an account, and paste the new ones’ emails into the box, one per line. Keep “Use the starting password”, or email them a link if they would rather choose their own.
- Test it yourself in a private window, as a client, before you send anything. Leave a test comment, check it lands on the Board, then delete it.
- Send the client the address, their email, the password and the link to the client guide. There is a template below.
Every project setting
Open a project with Edit. Every field, and what it is really for:
| Field | What to put in it |
|---|---|
| Name | What the client calls the job. It appears on the sign-in page, in emails and at the top of reports. |
| Short name | Lower-case letters, numbers and dashes. It goes in the install line and in links, and it is fixed once the project is saved. Use the client and the job: acme-website. |
| Site to review | The main address. Used for the “Open site” links and as the fallback when someone signs in without a page in mind. |
| Addresses allowed | Every address the site answers on, one per line, with https:// and no trailing slash. A request from anywhere else is refused, which is what stops a copy of the site on another domain from writing into your project. Add the live address too if the client will review after launch. |
| Starting password | The password new client accounts on this project are given. Make one suggests a readable password. Keep it per project: it means a reviewer on one job never holds the key to another. Change it whenever a client’s team changes. |
| Who can open the site | See the next section. |
| Feedback due | Shown to reviewers at the top of the panel. Leave empty if the project has no date. |
| Close to clients after that date | On the morning after the due date, clients can read but not add. Useful when a round has to be frozen before work starts. |
| Closed now | The same thing by hand, at any time. Diverse Media can still comment. |
| Clients can resolve or drop each other’s comments | On by default. Off means a reviewer can only close their own, and we can close anything. Turn it off where several people review the same site and one of them keeps closing the others’ points. |
| Space for this project | What the project’s screenshots, recordings and attachments may add up to, in MB. Leave empty for the standard 2000 MB. Once it is reached, uploads are refused with a message asking the reviewer to contact us; comments themselves still work. The project card shows how much is used, and turns red past 80%. |
| Clients see each other’s comments | On by default, and usually right: it stops two reviewers asking for opposite things. Turn it off when several parties are reviewing the same site separately and should not read each other, for example two competing sponsors. |
| Screenshot with each comment | On by default. About 0.1–0.3 MB per comment. Turn it off only for a site under heavy load or with material that must not be copied anywhere. |
| Recordings and attachments | On by default. Screen recordings and voice notes up to a minute, images and PDFs up to 20 MB. |
| Ask “first-time or returning visitor” | On by default. Matters on sites that remember a visit — an intro, a tour, saved settings. The site’s install line needs data-state-prefix="…" for it to do anything; our own builds add it. The quiet re-check every fifteen minutes never asks. |
| Guests | Off by default, and best left off. A guest signs themselves in with a name and an email, no password, and can then comment. Only available where the site is not behind Redline accounts. Use it for a workshop or a public consultation, never for a confidential preview. |
| Email new comments to | The Diverse Media people who should hear about every new comment on this project. Tick the producer and whoever is building it. |
Who can open a site
| Setting | What actually protects the site | Use it for |
|---|---|---|
| Redline accounts only | The guard files in the site’s own folder. Every request is checked; without a signed pass nothing is served, not even an image. Sign-ins and sign-outs are instant, and a disabled account is locked out within fifteen minutes. | Any staging site with client work on it. This is the default and the right answer nearly always. |
| Shared preview password | The Diverse Media password page, which we build into the site itself. Redline does not enforce this one; it is a note to us about how that site is protected. Comments still need a Redline account unless guests are on. | Sites built with the password page, usually where the client wants one link and one password for a group. |
| Public | Nothing. Anyone with the address sees the site; only commenting needs an account. | A live site, or a page that is public anyway and we want feedback on. |
Switching an existing project to Redline accounts only shows the Guard files box with the three downloads. Switching away from it does not remove the guard from the site — if you want the site opened up, take the guard lines out of its .htaccess as well.
Putting Redline on a website
Pick the case that matches the site. All three start the same way.
Before you start (every case)
- Create the project and give it a short name, the site address and a starting password.
- List every address the site uses under Addresses allowed, one per line:
https://acme.diversemedia.sg,https://staging.acme.com. Redline refuses every other address, including the same site onhttp://. - Choose who can open the site and save.
- Add the reviewers from the project card: More ⌄ → People on this project.
Case A · Public site: anyone may open it, clients comment
- In the project, choose Public and save. Copy the Install line:
<script src="https://redline.diversemedia.sg/review.js" data-project="acme-website"></script> - Paste it inside
<head>, above the site’s own scripts. On a site with one shared template, once is enough; otherwise it goes on every page. - WordPress: a header-code plugin such as WPCode → Header. Webflow, Squarespace, Wix: Site settings → Custom code → Head.
- If the site sends a Content-Security-Policy, add
https://redline.diversemedia.sgtoscript-src,style-src,connect-src,img-srcandmedia-src. - Publish, then run the check below.
Case B · Private staging site on our cPanel (…diversemedia.sg)
- In the project, choose Redline accounts only and save.
- A site Diverse Media builds: build it with Redline accounts on. The upload folder already has the
_redlinefolder, the.htaccesslines and the install line in the page. Upload it and go to the check. - Any other site: in the project, download guard.php, config.php and .htaccess lines.
- In the site’s folder on the server, make a folder called
_redlineand uploadguard.phpandconfig.phpinto it. - Open the site’s
.htaccess(File Manager → Settings → show hidden files). Paste the .htaccess lines at the very top, above everything else, and save. If there is no.htaccess, create one containing just those lines. - Paste the install line into the site’s
<head>as in Case A, so the Redline button appears once someone is in. - cPanel → MultiPHP Manager: the site must run PHP 8.1 or newer. Replacing an
.htaccesscan quietly put a domain back on an old PHP, which shows up as a 500 error. - Run the check below in a private window.
Keep config.php off email and off shared drives. It holds this project’s signing secret.
Case C · Site on the client’s own server
Their server runs PHP (most hosting, cPanel, Plesk, WordPress hosts). Send their web person the three files and these steps:
- Add the domain they will use to Addresses allowed first, exactly as it will appear.
- Create
_redlinein the website’s root and uploadguard.phpandconfig.phpinto it. - Paste the .htaccess lines at the top of the site’s
.htaccess(Apache or LiteSpeed). On Nginx, route every request except/.well-known/to/_redline/guard.phpthrough PHP-FPM. - Paste the install line into the site’s
<head>. - If the site sends a Content-Security-Policy, allow
https://redline.diversemedia.sgas in Case A. - The server needs to reach
https://redline.diversemedia.sgonce to fetch the signing key. Behind a strict firewall it cannot, and the site then shows “couldn’t confirm your sign-in”: download config.php from the project and upload it, as it carries the key or the secret the site needs.
Their server has no PHP (Netlify, Vercel, GitHub Pages, S3 and the like): the guard cannot run there. Either use Public with the install line, host the preview on our cPanel, or build it with the password page.
Check it works — do this every time
- Open the site in a private window.
- Case B and C: the Diverse Media sign-in appears first. Sign in as a client account on this project and you land on the page you asked for.
- The round Redline button is at the bottom right. Open it and leave a test comment.
- The comment appears on the Board, with a screenshot and the device it came from.
- Case B and C: sign out in Redline. The site asks you to sign in again. Now try an account that is not on this project: it is refused.
- Open the site on a phone and check the bar and the button behave.
- Delete the test comment.
If the install doesn’t work
| No Redline button | The install line is missing from <head>, or the site’s Content-Security-Policy blocks redline.diversemedia.sg. The browser console says “Refused to load”. |
| “This site’s address isn’t listed for the project” | The exact address, with https:// and no trailing slash, is not in Addresses allowed. The message names the host it saw; copy that. |
| The site opens with no sign-in | The .htaccess lines are not at the top, the file is not being read, or the host is Nginx and needs its own rule. |
| “This preview couldn’t confirm your sign-in” | The site has no key. Project → Edit → Guard files → download config.php and upload it into the site’s _redline folder. |
| The sign-in page loops | The site is not on HTTPS. Run AutoSSL for the domain. |
| PHP code appears on the page | PHP is not running for that folder. Set the version in MultiPHP Manager. |
| 500 error after uploading | Usually PHP has dropped to an old version with the new .htaccess. Set it to 8.1+ again. |
People and roles
| Role | Can | Cannot |
|---|---|---|
| Client reviewer | Open the projects ticked for them, comment, reply, resolve, drop, edit and delete their own, print reports. | See any other project, or the admin. |
| Client viewer | Open the site and read everything, print and export. | Add or change any comment. |
| Guest | Comment after signing themselves in with a name and an email, where guests are switched on. | Exist at all on a site behind Redline accounts. |
| Diverse Media staff | Every project, the Board, rounds, assignments, priorities, deleting any comment, adding and editing client accounts, adding and editing other staff. | Make someone an owner, change an owner’s account, or delete a project. |
| Owner | Everything, including making owners and deleting projects. | Change their own role, or disable themselves. |
Adding someone
- People → Add person. Name and email as they will use it.
- Pick the role, then tick the projects. The starting password shown next to “Use the starting password” is the one belonging to the first ticked project that has one.
- Choose how they get in: the starting password (quickest, and you can tell them on the phone), set a password now, or email them a link to choose their own, which works for seven days.
- Save. If mail cannot be sent from the server, the link is shown to you to pass on.
Several people on one project
On the project card, More ⌄ → People on this project lists every client account, with the ones on this project ticked first. Tick to add, untick to take someone off (their comments stay), and use Find to search by name or email. To add people who have no account yet, paste their addresses into Emails, one per line or separated by semicolons; Alice Tan <alice@client.com> uses the name as well. Anyone in the list who already has an account is simply added to the project, with the password they already have. Leave “Email people who already have an account” ticked and they get a short note saying the new site is open to them.
A client on more than one project keeps one account. If you type an email under Add person that already has an account, the box changes to adding projects to that account: their current projects stay ticked, you tick the new one, and their password is left alone. They sign in everywhere with the same email and password, their account page lists the sites it opens, and the comment panel names the site they are on. Each project still has its own starting password — the one they are first given is the first ticked project that has one.
Password on an existing person resets them to the project’s starting password or sends a fresh link. Disabled stops them signing in, and on a guarded site closes the door within fifteen minutes. Leave people disabled rather than deleting them when a project is finished: the history on their comments stays readable.
Briefing the client
Two minutes of clear instruction saves a day of support. Send this, adjusted, with the link:
Worth saying out loud on the call: they cannot break anything, small comments are better than long ones, and Edit text is the fastest way to handle wording.
The Board
Admin → Board, with a project picker at the top. Five columns: To do → In progress → For review → Resolved → Dropped. Drag a card between columns, or open it and set the stage there; on a phone, open the card.
| Column | What it means | Who sees it |
|---|---|---|
| To do | Landed, nobody on it yet. | The client sees nothing special. |
| In progress | Someone is working on it. Assign it so the client knows who. | The client sees “In progress” and the name. |
| For review | Done from our side, waiting for the client to agree. | The client sees “For review” and is nudged to resolve it. |
| Resolved | Closed. Counts towards “% closed” in the summary. | Visible to everyone. |
| Dropped | Not being done, with a reason. Always give the reason. | Visible, with the reason. |
Open a card for the whole picture: the screenshot, attachments, the recording player, the old-and-new text of an Edit text comment, the full history, the replies, and “Seen on” with the browser, system, window size, language and address. Go to opens the site at that exact spot.
On each card you can set an assignee, a priority (Low, Normal, High, Urgent) and a due date. Filter by person, device, priority, words, or an earlier round. Past rounds are read-only.
Select puts a tick box on every card. The bar that appears along the bottom is grouped: how many are picked and All shown on the left, then the stage and the assignee, then priority, then Export ⌄, with Delete set apart at the end so it is never next to something harmless. Everything applies to the cards you have picked, and delete asks first.
A workable routine
- When comments arrive, put anything that is not a change — a question, a misunderstanding — straight into a reply. Answering removes work.
- Group the rest by where they are in the build. Assign them.
- Move a card to For review only when it is live on the preview, not when it is done on your machine.
- Reply on the comment saying what changed. “Shortened to two lines and moved above the photo” takes ten seconds and prevents a second round on the same point.
- Chase anything sitting in For review before the next round starts.
Design & video projects
For designs, PDFs and films, make the project a Design & video project (the first choice in New project). Redline then serves the client a private, branded review page itself: no website, no install line, no guard. The kind can’t be changed once anyone has commented.
Setting one up
- The client. Under Settings → Clients, add the company once: name, brand colour and logo. Pick it in the project; their logo and colour go on the review page.
- The project. New project → Design & video. Choose the client, a starting password, and the overlay: the line along the bottom (default CONFIDENTIAL · FOR REVIEW ONLY · NOT FOR DISTRIBUTION), the viewer’s name tiled across, timecode on video, its strength, and whether approved versions can be downloaded.
- Prepare storage. On the project card, Media → Prepare storage. Redline makes the folders
video,imagesanddocuments, each with a read-me. Nobody makes or links folders by hand. - Add the reviewers with More ⌄ → People on this project, as for a website.
Putting files in
- The name gives the version.
Brand_Film_v1.mp4andBrand_Film_v2.mp4are versions 1 and 2 of “Brand Film”;Poster_v3.jpgis version 3 of “Poster”. Anything without a version number waits under Needs a name, where you give it a name and a number (the file itself isn’t renamed). - Small files: drop them on the Media dialog. They go up in pieces, so a dropped connection carries on.
- Large files: by FTP (FileZilla or similar). Media → Upload by FTP shows the server, username, password and the exact folder for each kind, with Copy buttons. Then press Check for new files (opening Media checks too).
- Nothing reaches the client until you press Publish. With “Email the reviewers when I publish” ticked, they get an email with a link straight to it the first time a version is published.
- Stage per version: Draft, For review or Approved. It is the stamp in the corner of every picture and frame. Approved versions can be downloaded by the reviewers if the project allows it, and each download is in the security log.
- × takes a version off the review page, and asks whether to delete the file itself too. Kept files move to Needs a name.
Video: the Redline review export
Export review copies as MP4, H.264, 1080p, constant frame rate, a keyframe every second, about 8 Mbps, “Fast start” / “Web optimised” on. In Premiere: H.264, Match Source frame rate, Key Frame Distance = the frame rate (25 for 25 fps), VBR 1 pass 8 Mbps. In Resolve: H.264, Keyframes every = frame rate, Quality 8,000 Kb/s, Network optimisation on. Redline reads each video when it arrives and warns under the file if it isn’t H.264, has a variable frame rate, has Fast start off, keyframes far apart, or is larger than 1080p. Frame stepping is only exact with a constant frame rate.
The overlay
On every picture, PDF page and video frame: client and project, deliverable, version and date (top left); the stage (top right); the line along the bottom; the timecode on video; and the viewer’s name, email and the time, faint, tiled diagonally and slowly drifting. Pictures are watermarked on the server, so a saved picture carries it. Video and PDF pages are drawn into one picture with the overlay, and comment stills carry it too. Nobody can stop a screen recording; the watermark names whoever made it.
Where the files are kept
With Bunny set up (below), files are kept in Bunny storage and played from Bunny’s network through links that expire after 30 minutes; nothing stays on the Redline server. Without it, they are kept on this server under data/media/, which is never served directly. A project keeps the storage it was prepared with.
Setting up Bunny (once)
- In Bunny: a Storage Zone in Singapore, and a Pull Zone connected to it.
- In the Pull Zone: Security → Token Authentication on (copy its key), and CORS on with
mp4,pdf,jpg,pngandwebpin its list (the overlay and the comment stills need it). - Add to
lib/config.phpon the server:'bunny_zone'(the storage zone name),'bunny_password'(its password),'bunny_host'(e.g.sg.storage.bunnycdn.com),'bunny_cdn'(the pull zone address, e.g.dm-redline.b-cdn.net) and'bunny_token_key'. Optional:'media_upload_max_mb'(the admin upload limit, default 1024). - Make a test project, prepare storage, upload a short video and check it plays, steps frame by frame and keeps a still with a comment.
Images and PDFs
Not everything is a website. On a project card, Images & PDFs takes posters, mock-ups, storyboards and PDF decks, up to 40 MB each.
- Upload the files. Give them names the client will recognise, because the name is what they see.
- Copy the review link —
redline.diversemedia.sg/view/<project>/— and send it. - The client clicks anywhere on the image or page and comments exactly as on a website. Each page of a PDF takes its own pins.
These comments join the same board, the same summary and the same export as the website ones, and are labelled with the file they belong to.
Rounds, exports and reports
Rounds
A round is one pass of feedback. On the site, open the Summary as staff and press Start a new round. Everything so far is archived under a name you give it (“Round 1 · first look”), and the site starts clean. Nothing is deleted: any round can be read again from the round picker in the summary and on the board.
Start a new round when a batch of changes is live and you want the next lot of comments kept separate. Don’t start one in the middle of a batch: comments from the same review then sit on both sides of the line.
Exports and reports
- Export → Spreadsheet (CSV), from a project card's More menu or from the foot of the panel on the site: every comment with its page, status, author, dates, device and replies. This is the one to put in a job folder.
- The same Export button appears on the board's select bar while several cards are picked, and gives a file of only those — for sending one page's worth to a writer or a developer.
- Export → Developer notes (text) (a project card's More menu, the board's select bar, or the Summary on the site): a Markdown text file, one section per comment, with the page, the CSS selector, the element, where in it the click landed, the animation moment, the device, the suggested wording and the links to the screenshots. It is meant to be handed to whoever writes the code, or pasted into an AI assistant as the brief. The printed PDF shows the same page and selector under each comment.
- Both exports are the same file wherever you take them from — the project card in the admin, the board's select bar, or the panel on the site. Same columns, same order.
- The conversation is included in full. Every reply with its author and the date, every earlier wording of an edited comment, and the reason given for a drop, all in their own columns (and their own section in the text file and the printed report). A Reply count column makes it easy to sort for the comments that turned into a discussion.
- The links to screenshots in that file are signed and last about a day. If the file is going into a job folder, download the images too.
- Print / PDF in the summary: a formatted report, marked confidential, grouped by page, with the counts at the top.
- Add screenshots before printing walks the site and takes a fresh picture of every comment. Worth doing for a client-facing report; it takes a minute or two.
Export before you delete anything, and at the end of a job. The server is not an archive.
Email notices
Sent from redline@diversemedia.sg:
| Goes to | |
|---|---|
| New comment | The staff ticked on the project under “Email new comments to”. |
| Reply | Everyone in that conversation. |
| Marked done, or dropped | The person who wrote the comment. |
| Assigned to you | The staff member it was assigned to. |
Every email links straight to the comment on the site. Anyone can switch their own notices off on their account page. If the server cannot send mail, invitation and reset links are shown to you in the admin instead, so nothing is stuck.
Working the comments well
- Reply to everything, even the ones you agree with. Silence reads as “ignored”.
- Never drop a comment without a reason. “Out of scope for this round, noted for phase two” is a reason. A blank drop looks like a shrug.
- Answer questions on the thread, not by email. The next person to read it is then not missing half the story.
- Keep our own notes in Redline too. A comment from us on our own site is a fine way to leave a note for the builder, and the client sees it is being handled.
- Watch the due date. If a client is silent two days before it, send a nudge with the summary link.
- Use priority honestly. If everything is urgent, nothing is.
Updating the server
The only copy of Redline is DM-Redline in our repos folder. Edit it there; never keep a second copy in Downloads.
- Change the files in
server/. - Upload only the changed files to
redline.diversemedia.sg, replacing the old ones. Turn on Show hidden files in File Manager so.htaccessand.user.inigo up too. - Never upload
data/. That is where accounts, comments and screenshots live. Theserver/data/folder here is only the empty, protected one for a first install. - Never replace
lib/config.phpon the server. It holds that server’s keys. - Reload the admin with Ctrl+F5 once, then check the sign-in page and one project.
When review.js or review.css changes, sites pick it up on their next load; they are served with no-cache for exactly that reason. When guard.php changes, each guarded site needs the new copy in its own _redline folder — config.php there stays as it is.
Backups, storage and limits
- Back up
data/with the rest of the cPanel backups. Everything is in there; nothing is anywhere else. Each change also leaves a.bakof the file as it was before. - Sizes: screenshots 0.1–0.3 MB, recordings roughly 1–7 MB a minute, attachments up to 20 MB, uploaded designs up to 40 MB. A busy project runs to a few hundred megabytes.
- Each project has a ceiling, 2000 MB unless you change it, and the project card shows how much is used. One person is also limited to 80 uploads an hour, so nothing can run away while you are not looking. Watch the cards on a project with long recordings.
- Uploads that are never posted are swept after a day. Deleting a comment deletes its files at once.
- If recordings fail to upload, raise
post_max_sizeandupload_max_filesizeto 48M in cPanel → MultiPHP INI Editor..user.iniasks for this already, and some hosts ignore it. - Delete finished projects once the job is closed and exported. It is the only way storage comes back.
What is stored, and how
- Passwords are kept only as bcrypt hashes. Sign-in tokens are random, and only their SHA-256 is stored. A session lasts 30 days, and changing a password signs out every other device.
- Eight wrong passwords in fifteen minutes pause that address for fifteen minutes. Asking for a reset link has its own limit and cannot be used to lock anyone out.
- Forgot password answers the same way for every address, so it cannot be used to find out who has an account.
- A project answers only the addresses listed for it. The admin works only on
redline.diversemedia.sg. lib/anddata/are blocked from the web. Check after any install that/lib/config.phpand/data/users.jsonboth return 403.- Uploads are checked by their actual content, not their name, and are served with no-sniff headers in a sandbox, so a file cannot pretend to be something it is not.
- The guard signs each visit with the project’s own key. That key lives in
lib/config.phphere and in the site’s_redline/config.php, and nowhere else. Treat both as passwords.
Visits and Activity
Every signed-in visit to a project is recorded for security: who, when it started, roughly how long the site stayed on their screen, device, browser and network address. The sign-in box on the site and the private-site sign-in page both say so, and the client guide explains it. Open it from the project card: More ⌄ → Activity.
- Choose the period (7 days, 30 days, 12 months). Show leaves out Diverse Media’s own visits unless you ask for them.
- The line at the top names anyone on the project who hasn’t visited yet, which is the quickest way to see who to chase before a deadline.
- Press a name to see each visit. On the site now means they checked in within the last 11 minutes.
- How it is measured: the page checks in when it opens, every five minutes while it is on screen, and as it leaves the screen. Eleven quiet minutes end a visit. Two tabs open at once count once towards the total. A tab left open on a screen nobody is looking at still counts, so treat the times as a guide.
- Only people who are signed in are recorded. Someone who opens a site with a shared preview password and never signs in to comment is not.
- Export gives a spreadsheet with one row per visit, or a short text summary to paste into an email.
- Records are deleted after 12 months, and with the project. They are for security and for knowing when a preview has been seen; don’t share one client’s visits with another.
The security log (owners)
Owners have a Security log tab next to Settings. Staff don’t see the tab, and the server refuses them if they try to open it (the attempt is logged). It holds, for the whole server:
- Every sign-in and every attempt: on the admin, the account page, the sign-in box on a client site and the private-site sign-in page, with the reason a failed one failed (no such account, wrong password, account disabled, no password yet), and lockouts after too many tries.
- Private-site entries and refusals, and sign-outs. The quiet 15-minute re-checks are not listed.
- Passwords: reset links asked for and used, invites accepted, passwords changed, and expired links tried.
- Changes: accounts added or changed (role, projects, disabled, how they got a password), people added to or taken off a project, project settings changed (a starting password shows only as “changed”), projects added, deleted or imported into, each with who did it, and anything the server refused.
Each line has the time, the network address and the browser. Filter by period and kind, search by name, email, address or project, and use Export for a spreadsheet or a text version. Lines are kept for 12 months and then deleted. Passwords are never written to it. Several failed sign-ins from one address for different accounts is the pattern to act on: disable the accounts concerned or ask the host to block the address.
Deleting things
- A comment: its author or any staff member, from the comment or the board card. Its screenshot, recordings and attachments go with it.
- A person: disabling is usually better than deleting, because their name stays on their comments.
- A project: owner only. Edit project → Delete project, then type the short name to confirm. Comments, rounds, screenshots, recordings, uploaded designs and everyone’s access to it go for good. Export the CSV first.
When something goes wrong
| Client: “that email and password don’t match” | Check the address is the one on their account, and that they are not on a different project’s password. After eight tries the account waits fifteen minutes. Reset it from People → Password. |
| Client: “this account doesn’t have access” | The project is not ticked for them. People → edit them → tick it. It takes effect immediately. |
| Client can’t stay signed in | Their browser is blocking cookies for the preview. Strict tracking protection or a private window with a blocked cookie jar does this. Another browser confirms it in a minute. |
| “This preview couldn’t confirm your sign-in” | The site lacks the key. Edit project → Guard files → config.php → upload into the site’s _redline. |
| Comments not arriving by email | Check that redline@diversemedia.sg exists, that you are ticked under “Email new comments to”, and that your own notices are on. Links are shown in the admin when mail fails. |
| Admin shows 500, or a blank page | PHP version. MultiPHP Manager → 8.1 or newer for the subdomain, then reload with Ctrl+F5. |
| Board or panel looks unstyled | An old stylesheet is cached. Ctrl+F5. If it persists, the CSS did not upload. |
| Screenshots are blank on one site | The page draws in a way html2canvas cannot read, usually a video or a cross-origin image. Ask the client for a recording instead, and note it on the project. |
| A comment’s pin is in the wrong place | The page changed since it was left. The screenshot shows what they saw; use Go to and the page label to place it. |
Words we use
| Project | One client website, or one set of images and PDFs, with its own people, comments and settings. |
| Install line | The single <script> tag that puts Redline on a site. |
| Guard | The PHP file in a site’s _redline folder that keeps everyone but our reviewers out. |
| Pass | The signed note the guard gives a browser after a successful sign-in. It lasts twelve hours and is re-checked every fifteen minutes. |
| Round | One pass of feedback. Starting a new round archives the previous one. |
| Anchor | What a comment is pinned to: the element, and where it was on the page, plus the animation moment or 3D view if there was one. |
| Moment | The second of an animation a comment was left on. |
| Starting password | The password a project hands to new client accounts. |
Diverse Media Pte Ltd · +65 6671 1466 · info@diversemedia.sg