Introduction
If you are using ChatGPT to build an internal system for your business, give it the information in this guide before it writes any code. That way, what it builds will run on your iSeek hosting, stay secure, and be easy to maintain and upgrade later.
We call these systems intranets: private, login-only platforms for your own team rather than the public. Typical examples include a staff portal at staff.yourcompany.ie or a customer relationship manager (CRM) at crm.yourcompany.ie.
The sections below explain what we provide, which technologies to use, and the standards ChatGPT should follow. There is also a ready-made prompt you can copy and paste to get started.
Your hosting environment
iSeek already hosts your website, your domain name and your DNS, so we can set up everything your intranet needs on our servers. Here is what we provide:
- A subdomain such as staff.yourcompany.ie or crm.yourcompany.ie, created and pointed to your hosting space.
- An SSL certificate for that subdomain, so all traffic is encrypted over HTTPS.
- Dedicated web space on our server where the intranet’s files live, separate from your main website.
- A MySQL database for the intranet’s data, with its own username and password.
- A control panel (Plesk) on a managed Linux server, which we look after day to day.
Tell ChatGPT that this is managed web hosting on Plesk, not a server you control. It should not assume it can install system software, run Docker, or change server-wide settings. Node.js and the Laravel PHP framework are both available through Plesk, but our recommended approach is a standard PHP and MySQL application. If ChatGPT suggests Node.js or anything beyond PHP and MySQL, check with us first so we can confirm it is set up correctly on your plan.
Costs and hosting plans
There is no additional cost to create the subdomain or its SSL certificate. The intranet shares the disk space of your existing hosting plan, so if it stores a lot of files or data, you may need to upgrade to a larger plan to make room.
If the intranet will be mission-critical to your business, we recommend upgrading to one of our Performance or High Performance hosting plans. These give greater resources and newer technologies to both your website and the intranet subdomain.
Technology stack
Your intranet must be built on a LAMP stack, which is what our servers run.
| Component | What to use | Notes for ChatGPT |
| Linux | Provided by iSeek | Use relative file paths; don’t rely on server-level configuration |
| Apache | Provided by iSeek | Site-level settings go in an .htaccess file |
| MySQL | MySQL / MariaDB database | Use PDO with prepared statements for all queries |
| PHP | PHP 8.3 or above | Write modern PHP; avoid deprecated functions |
Ask ChatGPT to keep passwords and database details in a single configuration file stored outside the public web folder, or protected from web access. Any third-party libraries should be managed with Composer, and the list of them included with the project.
What ChatGPT must build in
These are the minimum standards for any intranet we host. Make sure ChatGPT includes each one from the start; adding them later is much harder.
User accounts and access levels
- Every person gets their own login. No shared accounts or shared passwords, ever. This lets you see who did what and remove access when someone leaves.
- Different levels of account. An Admin level at the top has full access to the whole system, including managing users. Below that, create levels suited to your business, for example Manager, Staff and Read-only, each seeing only what they need.
- Admins can add, suspend and remove users without needing a developer.
Security
- Two-factor authentication (2FA) using an authenticator app such as Google Authenticator or Microsoft Authenticator. At a minimum, require it for Admin accounts.
- Secure password reset by email, using a one-time link that expires.
- Strong password storage using PHP’s built-in password_hash() function. Passwords must never be stored in plain text.
- Login protection that locks or slows down repeated failed login attempts.
- Protection against common attacks, including SQL injection, cross-site scripting (XSS) and cross-site request forgery (CSRF).
- Secure sessions that time out after a period of inactivity and work only over HTTPS.
- An activity log recording logins and important changes, so you can see who did what and when.
Keep it off search engines
The intranet is private and should never appear on Google or any other search engine. ChatGPT should add a noindex rule in all three of these places:
- A robots.txt file that disallows all crawling
- A noindex, nofollow robots meta tag on every page
- An X-Robots-Tag: noindex, nofollow header, set in .htaccess
Every page other than the login and password reset pages should require the user to be logged in.
Documentation
- A README explaining what the system does, how it is structured, and how to install and configure it.
- Clear comments in the code, so another developer, or ChatGPT in a later conversation, can understand it.
- A changelog listing what changed in each version.
Version control and future upgrades
- Keep the code in Git, ideally in a private GitHub or Bitbucket repository, so every change is tracked and can be rolled back.
- Use version numbers (for example 1.0.0, 1.1.0) and record each release in the changelog.
- Manage database changes with migration scripts, so the database can be upgraded safely without losing data.
- Keep configuration separate from code, so updates never overwrite your settings or passwords.
Starter prompt for ChatGPT
Copy the text below into ChatGPT at the start of your project, then describe what you want the system to do. Replace the parts in square brackets.
| I want to build a private intranet system for my business: [describe what it should do, e.g. a staff portal for rotas, documents and announcements / a CRM to manage customers and enquiries].
HOSTING – It will run at [subdomain, e.g. staff.mycompany.ie] on managed hosting provided by iSeek (Plesk on Linux). – The subdomain will have an SSL certificate, so everything runs over HTTPS. – I cannot install system software, run Docker, or change server-wide settings. Node.js and Laravel are available through Plesk if needed, but a standard PHP and MySQL application is preferred. TECHNOLOGY – LAMP stack: Linux, Apache, MySQL, PHP 8.3 or above. – Use PDO with prepared statements for all database queries. – Use .htaccess for Apache settings and Composer for any libraries. – Keep database credentials and settings in one config file outside the public web folder, or blocked from web access. USERS AND ACCESS – Every user has their own individual login. No shared accounts. – Role-based access levels: Admin (full access to everything, including managing users), plus lower levels such as [e.g. Manager, Staff, Read-only]. – Admins can add, suspend and remove users. SECURITY – Two-factor authentication using an authenticator app (required for Admins at minimum). – Secure password reset by email with an expiring one-time link. – Hash passwords with password_hash(). – Rate-limit or lock out repeated failed logins. – Protect against SQL injection, XSS and CSRF. – Secure sessions that time out after inactivity. – Log logins and important changes. PRIVACY – This must never appear on search engines. Add robots.txt disallowing all crawling, a noindex/nofollow robots meta tag on every page, and an X-Robots-Tag noindex header in .htaccess. – Every page except login and password reset requires the user to be logged in. DOCUMENTATION AND VERSIONING – Comment the code clearly and provide a README covering structure, installation and configuration. – Set the project up for Git version control with version numbers and a changelog. – Use database migration scripts so future upgrades don’t lose data. Please start by proposing the structure of the system and the database before writing code. |
Launching your intranet
When your system is ready, ask ChatGPT for step-by-step launch instructions for iSeek’s Plesk hosting. These should cover uploading the files, creating and importing the database, setting up the configuration file, and creating the first Admin account.
We are happy to help with any part of the launch, including:
- Setting up the subdomain and its SSL certificate
- Creating the MySQL database and database user
- Installing the files on the server and checking that everything works
There may be a small fee for this work, depending on how much time it takes. We will review it with you at the time, before any work starts.
We can also help and guide you with future updates or changes to the platform, whenever you need them. Just get in touch with the iSeek team at iseek.ie.