What IP Access Rules do for your team
IP Access Rules let you decide where users can sign in from. Instead of relying on passwords alone, you can set network-based access policies that allow logins from trusted locations and stop attempts from anywhere else. For a business with staff in Woodstock, Johannesburg, Pretoria, Durban, Gqeberha or remote roles nationwide, that gives you a clearer boundary around who can reach company accounts.
This is especially useful where teams work from a mix of office, home and travel locations. If someone tries to sign in from an unknown range, the login can be denied even if the correct password is entered. That extra control helps reduce exposure from stolen credentials, shared accounts and weak home network practices.
- Allow access by office IP range, home range or VPN exit point
- Block unknown or unapproved networks automatically
- Support a cleaner access policy for small teams and contractors
- Make access decisions easier to audit during quarterly reviews
Where IP rules fit best in South African small business setups
This feature suits businesses that want tighter control without making day to day work difficult. It is common for finance teams, operations staff, directors, outsourced bookkeepers and support teams to need access from different locations. IP Access Rules help you separate those use cases properly instead of giving every user the same level of access from anywhere.
They are a strong fit for firms that handle client data, supplier portals, banking, payroll, legal records or internal admin tools. If your team works between a Cape Town office and remote staff in other provinces, the rules can be set so only approved networks are accepted. That is useful where load-shedding changes routines and people shift between office, fibre at home and mobile connections, because the policy can still stay consistent.
- Office based teams with a fixed IP from the router or firewall
- Hybrid teams that use approved home or VPN ranges
- Businesses that need stricter control for admin and finance users
- Growing teams that want clearer access rules before adding more systems
Options and rule types you can set up
IP Access Rules are usually set around one or more trusted ranges. That can be a single fixed IP address, a block of addresses, or separate rules for different branches and user groups. A practical setup often starts with the main office and then adds approved remote ranges for specific staff. If your team has seasonal workers or external support users, you can also limit those accounts to narrower ranges or time based access through your broader admin process.
Most small businesses use a simple structure: office range for staff on site, VPN range for remote users, and a separate rule set for administrators. You can also keep stricter rules for sensitive roles and more flexible ones for users who only need limited app access. The aim is to cut down on risk without creating admin headaches.
- Single IP allow list for one office or branch
- IP range rules for multiple addresses at the same site
- Separate rules for staff, admins and contractors
- Optional pairing with SSO policies and user group controls
Setup requirements and what your network must have
There is no special power or gas requirement for IP Access Rules themselves, but your site network must be properly documented. For an office setup, you need a stable public IP address from your internet service provider or a reliable VPN gateway that presents a known address. If the connection changes often, the rules can become harder to manage, so a fixed connection is usually better for head office and critical staff.
Before rollout, check your router, firewall and remote access method. You should know which IP address the office presents to the internet, which users will work remotely, and whether anyone is using a mobile hotspot or shared connection. In some cases a business will need to update its internet setup first, especially if the public IP changes after power interruptions or router resets.
- Fixed public IP preferred for offices and branch sites
- Approved VPN endpoint for remote staff if required
- Documented user groups for different rule sets
- Clear fallback process for lockouts and travel exceptions
Installation, onboarding and admin handover
For South African teams, a sensible rollout starts with an Initial Security Review, then Platform Setup, SSO Configuration and Permission Mapping. After that, IP Access Rules are added and tested against the real working setup. This includes office logins, remote users, mobile use and any planned travel access. The point is to confirm that legitimate users can get in while unknown networks are blocked cleanly.
Training matters here because IP rules affect day to day support. Admins need to know how to add a new branch, allow a temporary travel range, or respond when a user is locked out after changing internet providers. Our team supports remote onboarding nationwide, with Johannesburg Support, Pretoria Support, Durban Support and Gqeberha Support available for businesses that want a local point of contact.
- Initial Security Review before rules are applied
- Admin Training for changes, exceptions and user support
- User Onboarding Training so staff know what to expect
- Remote Rollout Support for teams in multiple provinces
Admin, support and what to confirm before rollout
IP Access Rules need light but regular care. At least once a quarter, check whether your office IP has changed, whether any staff have moved location, and whether new branches or VPN points need to be added. If a business changes internet provider, upgrades a firewall, or moves premises in Cape Town or Pretoria, the trusted range may need to be updated straight away. That is part of a proper Quarterly Access Review.
Before ordering, confirm the number of users, the offices that must be allowed, and which roles need stricter controls. Also check whether your team uses static IPs, dynamic home connections or a VPN service. If anyone travels often, you may need an exception process for those cases. Good planning prevents avoidable lockouts and saves time for support staff.
- Confirm user count and admin count
- List all office, branch and remote connection points
- Check whether public IPs are static or dynamic
- Plan exception handling for travel and temporary work sites
Key facts
| Feature | Network-based login control for approved IP addresses and ranges |
|---|---|
| Typical use | Small business teams using password management and SSO |
| Rule types | Single IP, IP range, office allow list, VPN endpoint allow list |
| Best fit | Hybrid teams, finance users, admins and multi-branch setups |
| Setup requirement | Stable public IP or approved VPN gateway |
| Review cycle | Quarterly access review recommended |
