Re: Django admin suitable for external users?

I agree that for widespread "unknown" customers its probably not good. I think that when working in close partnership with a small number of clients/customers (the way the funding is works is not really a big issue), who will receive training and a good user manual, then the admin (with some

Re: Django admin suitable for external users?

Derek, my distinction would be based product ownership ... potentially both would or could pay. So in other words "clients" would own the product as their own, versus "customers" whom are paying for service without ownership and control of product development. I have seen Django admin opened

Re: Django admin suitable for external users?

What is the difference between a customer and client - I assume the former is paying? On Monday, 5 October 2015 22:12:14 UTC+2, ta...@pingmd.com wrote: > > Has anyone opened Django admin to customers, not just clients? If so, what > warranted such decision as appose to only exposing partial

Re: Django admin suitable for external users?

Has anyone opened Django admin to customers, not just clients? If so, what warranted such decision as appose to only exposing partial functionality through a customized app? -- CONFIDENTIALITY NOTE: The information contained in this transmission may be privileged and confidential, and is

Re: Django admin suitable for external users?

I'd say for non-technical users, you may want something custom; particularly if they are only working with a smaller sub-set of the data. We have users that are fairy technical (working in the science domain) that are used to large grid-like data displays (typically in spreadsheets). So, for

Re: Django admin suitable for external users?

Thanks Ryan. That's an interesting additional consideration. I don't think we're particularly married to Django admin as an open interface to the database where I work, although I can see how that wouldn't always be the case. Also, I think Luis's suggestion could help to quell the resistance

Re: Django admin suitable for external users?

It really depends on the project you're working on. The resistance comes mostly from developers who utilize the admin as an open interface to the database with minimal restrictions. I like to use the admin this way for large projects that are used by many people, building out a custom "staff"

Re: Django admin suitable for external users?

Sure, you could have several admin site with the same models. I read an specific page about how to do that, but right now can remember what is the specific url. Those other links could help you. https://docs.djangoproject.com/en/1.8/ref/contrib/admin/#the-register-decorator

Re: Django admin suitable for external users?

That's an interesting idea. Thanks. I suppose it's possible to register models with two different admin sites, although I've never tried doing that myself. On Wednesday, September 23, 2015 at 5:21:04 PM UTC-4, luisza14 wrote: > > I suggest you to create a custom admin site for your external

Re: Django admin suitable for external users?

> > How technical are your users? Not very technical, necessarily. They're normal end-users. What are your security constraints? We're in the medical industry, so security is a key consideration for us in general. I think the main concerns about Django admin specifically were that it

Re: Django admin suitable for external users?

I suggest you to create a custom admin site for your external user where you expose only the models that interact with the external user and create a middleware for forbidden access to the other admin site. 2015-09-23 14:49 GMT-06:00 Bill Freeman : > How technical are your

Re: Django admin suitable for external users?

How technical are your users? What are your security constraints? How much work can you do to make it "pretty"? (Believe me, someone will ask.) Are there fields that you want to administer internally but don't want to expose to the users? Will your users object if you decide to move to a newer

Django admin suitable for external users?

Hello! I just had a fairly lengthy conversation with my colleagues about whether or not Django admin is well-suited to external users outside our company. I took the position that for certain use-cases, exposing Django admin to third parties makes a lot of sense, given that the admin