Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 482
    • Issues 482
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4839

Closed
Open
Opened Nov 06, 2017 by Ron Granger@RonGranger

[Feature Request] Multiple Clients (per site)

Hey, I am using ISPConfig for a few days and already found some limits so I can't replace my dirty-coded Admin-System yet.

For some projects I got a lot of clients for one site so I would need to connect something with more than one client - that seems impossible at the moment.

My Idea would be to create a group of clients (let's call it 'project' for now, 'team' would also be a fitting name). Let's imagine there are 5 persons working on my 'project'. I create the first site for this 'project' and instead of a client I connect the 'project' with it so every client connected to this project can access the connected stuff. Later I want to create a second site (may be another subdomain) and I connect it to the 'project' as well. Everything works fine ;-)

I think this would be the easiest solution because manually adding all the clients is a waste of time and seems harder to implement in the code.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4839