I actually ran into a similar issue whilst designing one of my own apps earlier this year.
One thing I want to point out immediately is that common practice for mobile interfaces is to have tabs at the bottom of the screen or below a heading and navigation buttons. In the case of Apple, if you don't follow the strict UI guideline of having tabs at the bottom, your app may not even get accepted into the App Store. I'm not entirely sure what platform you plan on distributing your app, but I wanted to point this out first. I highly recommend checking out the Apple Human Interface Guidelines, and the Android Design Guidelines to see if you need to make changes to your layout.
In regards to your question about page tabs, I highly recommend you stick to your current plan because they are a crucial part of many mobile interfaces. It's whether you choose to use Tabs to display "dead-end" pages (pages that don't provide navigation to another page), or a separate view hierarchy with multiple pages. To best determine your best option, you must consider a few simple things:
Think of each Tab as a category. Your "Users" tab should only contain views (pages) relating to creating users, modifying users, etc. Giving a tab a broad name allows you to still convey what "area" of your app the user is currently within, and allows you to display many pages whilst that tab is highlighted. If you have many similar views, you should have multiple pages in a tab. You will also want to provide a way for the user to back-out of a hierarchy of views, and eventually lead to the original view that the tab presents - otherwise this becomes unintuitive and hard for the user to navigate.
If you only present a single page for each tab, you should look into pop-ups or lightboxes that display over the original page, because otherwise you're not going to have a logical place for any corresponding User pages to go. Popups that cover the entirety of the page (including the Tab Bar) work perfectly fine. They are not unintuitive and present a direct request for input from the user - and this is also quite a common practice.
In my example, I was creating an app for a live event that occured in my local area. It needed to have multiple tabs for Food vendors, entertainment information etc., and I wanted to be able to provide more information on specific food vendors when they were tapped. I made a detail view and filled labels accordingly, and added back buttons so that the original page could be accessed, and a tap of the tab would also pop back to the original page in the hierarchy. I found this worked well for my app and met all of Apple's guidelines in my case.
Let me know how you go, and if you have any other questions!