IP Limitations for Enterprise: Corporate Security and Safety Use Cases

Most security conversations start with passwords. But for an organization account — especially one used by students or holding sensitive records — where a login comes from matters as much as who it claims to be. IP limitation lets an organization admin confine access to the networks you trust: anyone in scope can sign in only from an address you’ve listed, and every other address is turned away. The check runs the moment someone tries to get in.

How the control works

You add the IP addresses you trust — your campus or office network, for example — and then choose who is held to that list. Anyone in scope can connect only from a listed address; every other address is blocked.

• All — everyone in the organization is held to the list. The account is reachable only from your trusted addresses.
• Only Group — only members of a selected group are held to the list. Your students, for instance, can sign in only from the school network, while staff and admins are unaffected.
• Only Member — only one specific user is held to the list, matched by user ID.

DocupletionForms is deterministic by design: a rule either matches or it doesn’t. IP limitation works the same way — an incoming address is on your list or it isn’t, and the outcome is identical every time. There’s no scoring and no machine-learning judgment call to second-guess.

Keeping a classroom on campus

For schools, this is the use case that matters most. Students learning document-process encoding can be held to the school network with Only Group applied to your student group, or with Only Member for an individual account: they can sign in and work only from campus. Off-campus addresses simply can’t reach the students’ accounts.

The point is to keep the learning environment — the forms students build and the work around them — inside the school and under supervision, rather than open to the outside world. A classroom practicing on the platform stays a closed, on-campus space instead of something reachable from anywhere on the internet.

• Confine the student group. Apply Only Group to your students so their accounts work only from the school network — the rest of the organization is untouched.
• Protect a records-holding account. Use Only Member to hold a registrar or records-admin login to your approved campus network.

More corporate security use cases

• Lock the whole org to your network. With All, the account is reachable only from your office network or VPN range — nobody signs in from anywhere else.
• Hold contractors to approved locations. Apply Only Group to contractors, temps, or interns so they connect only from listed addresses, while full-time staff stay flexible.
• Tighten high-value accounts. Pin a finance or admin login to one location with Only Member, so that sensitive account can’t be used from anywhere off your list.
• Blunt credential theft. Even if a password leaks, a stolen credential is useless from an address that isn’t on your list.

What IP limitation does — and doesn’t — touch

IP limitation is an access control. It governs who can reach your account at login and organization switch, and nothing further along. The way your intake data maps into your PDF documents is unchanged: that engine is rule-based and runs identically for every permitted user. Confining access controls the front door; it doesn’t alter what happens once a trusted user is inside.

It’s also one layer, not a whole strategy. IP limitation pairs well with strong passwords and disciplined user management, but it isn’t a substitute for them — treat it as part of a defense-in-depth approach rather than the entire wall.

Turning it on

An organization admin can set this up in a few minutes: sign in with the admin account, open Organization Settings, go to the IP Restrictions section, add the address you want to allow, choose the scope, and save. The full walkthrough lives in our guide.

Read the IP Limitation guide