# Logical structure ### Structure #### Your workplace and its clients The [workplace](/zipwire-approve/unboxing-key-concepts/workplaces.md) in Zipwire represents the business or organization that manages everyone, assigns work to workers and creates teams of approvers and processors. The workplace has an Administrators Team and its members have full rights over the workplace. In more unusual cases, a user may be an administrator of more than one workplace. If so, additional UI controls will appear to allow that user to switch between the workplace they're acting upon. As in real life, the workplace can (and likely does) have many clients, and each client can have many assignments. #### Assignments and teams The [assignment](/zipwire-approve/unboxing-key-concepts/assignments.md) is a collection of settings about what the name of the assignment is and who the senders are, and who will approve and process their timesheets. When you go first setup your workplace, you'll be taken through some steps to create your first assignment. This will also create two new [teams](/zipwire-approve/unboxing-key-concepts/teams-and-inboxes.md) for its approvers and processors–each time you create a new assignment, Zipwire will create two new teams. The teams are actually independent of the assignments and are logically just children of the workplace. This means you can use the same team to approve or process many assignments. If you're a staffing agency, you may want a single team for all the people who process timesheets, and you can do this. It's possible to switch the entire team that does the processing (or approving) on an assignment. Teams can be renamed anytime, or deleted, once it has no assignments and no members. #### Organizing with assignments You can use [assignments](/zipwire-approve/unboxing-key-concepts/assignments.md) however you wish to break up groups of senders, approvers and processors. {% hint style="info" %} Usually it's the approvers that determine when to make another assignment, just as in a company, it's the line managers that lead groups of people. {% endhint %} In general, people tend to work under a line manager who may have a deputy. These people would approve people's timesheets and so they would have an assignment for their team, and that would have a Zipwire team holding the line manager and her deputy. Another reason to create or even split an assignment up is because of different configuration. This is rare because each sender can have their own [rate plan](/zipwire-approve/unboxing-key-concepts/rate-plans.md), and each rate can have its own [billing plan](/zipwire-approve/unboxing-key-concepts/billing-plans.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zipwire.io/zipwire-approve/logical-structure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.