The crafts

A craft is the description of a job, written in enough detail that whoever fills it knows what they do, what they need, what they cannot do alone and who they hand their work to. It is not an employee: it is the template. The employee is the role, which is born from a craft and then adjusted to this company.

The tab is called Roles, inside Settings (the page address is perfiles). Its heading is «Crafts ready to use».

The header

Element	What it shows
Title	«Crafts ready to use».
Summary	«N crafts · M work areas». N counts every craft in the catalogue; M, the distinct areas that appear in them.

Fifty-four crafts ship out of the box. The real number is the one in the header: the catalogue can grow without touching the application.

The filters

Element	What it does
Search box	«Search for a craft…». It searches the title, the mission and the craft’s area. It does not search skills.
«All»	Clears the filter. It is the one selected when you arrive.
«From the company»	Shows the crafts on the chain of command and hides those of your control team.
«Your control team»	Shows only the crafts whose scope is «control».
One button per area	One filter for each area that appears in the company’s crafts. Press it and you only see that area.

The filter is exclusive: choosing an area hides «All». If the search finds nothing, «No craft matches that search» appears.

Each craft’s card in the list

Part	What it shows
Title	The craft’s name, for example «Mercantile lawyer».
Tag	The area, or «control» if it belongs to your control team.
Mission	The sentence that sums up why that craft exists.
Footer	Its skills, separated by dots, and «· N sources» if it brings reference addresses.
«View» button	Opens the full craft.
«Add» button	Opens the form to hire it.

What a craft carries inside

These are all the fields a craft stores. Some show on screen and others are carried over to the role when you hire it.

Field	What it is	Where you see it
`codigo`	The internal identifier, lowercase and hyphenated (for example `abogado-mercantil`).	Not shown; it links records and tells you which craft a role came from.
`titulo`	The craft’s name and the role’s default job title.	In the list and in the dialogue header.
`area`	The work area.	In the card tag and in the filters.
`mision`	Why the craft exists, in one or two sentences.	First line of the «View» dialogue.
`directrices`	The long text with what it does, its rules, when it escalates and what it delivers.	In the «View» dialogue, in sections.
`contexto`	The ground it works on: regulation, sector and conventions.	Section «The ground it works on», when the craft carries it.
`habilidades`	What the role will know how to do: read, remember, write, execute, delegate or browse.	In the card footer and in «What it gets when you hire it».
`reporta_a`	Who it depends on by default: `ceo` or `propietario`.	In «What it gets when you hire it», as «depends on you» or «depends on Adrián».
`urls`	Reference web addresses, each with a title and a value.	Section «Where it gets its information» and the source counter.
`documentos`	Reference documents, in the same format as the URLs.	Not shown in the dialogue, but they are copied to the role as sources of type «Document».
`origen`	Where the craft’s inspiration came from.	At the end of «What it gets when you hire it».
`ambito`	`empresa` or `control`. It decides which branch of the org chart it falls in and which filter shows it.	In the «control» tag and in the dialogue subtitle.

The areas the catalogue uses are these:

Code	Name on screen
`legal`	Legal
`fiscal`	Tax
`pagos`	Payments
`redes`	Social media
`calidad`	Quality
`seguridad`	Security
`plataformas`	Platforms
`finanzas`	Finance
`datos`	Data
`personas`	People
`ventas`	Sales
`marketing`	Marketing
`soporte`	Support
`producto`	Product
`operaciones`	Operations
`documentacion`	Documentation
`estrategia`	Strategy
`tecnologia`	Technology
`control`	Control
`general`	General

The «View» dialogue

It opens from a card’s «View» button. It carries the craft’s title and, below it, the area and «from Adrián’s team» or «from your control team».

The content reads in this order:

The mission, as a standfirst.
The ground it works on, if the craft brings context.
The guidelines, in sections. The text is split by lines: a normal line is a heading and the lines that start with «- » are bullets of that section. If the text starts straight with bullets, the section is titled «What it does». In the factory crafts you will see, for example, «What you do», «Rules», «When you escalate» and «Deliverables».
Where it gets its information, if it brings sources: each one with its title, its address and a link that opens in another tab.
What it gets when you hire it: the skills, who it depends on and the origin.

At the bottom there are two buttons: «Close» and «Hire this craft», which leads to the same form as the «Add» button.

If you open the address with ?oficio=codigo, that craft’s dialogue opens on its own. Useful for linking to it or showing it without searching.

The «Add» dialogue

This is the step from craft to role. It carries the title «Add: craft name» and this explanation: «It starts with the craft already written. You can change whatever you like afterwards».

Field	What it is	How it comes
Person’s name	The role’s proper name.	Empty and optional. Without a name, it is called by its job title.
Job title	The role’s title.	Filled with the craft’s title; you can change it.
Depends on	Who it hangs from.	«Adrián (CEO)» if the craft belongs to the company; «You (control team)» if it is a control one.
Mission	A reminder of the craft’s mission.	Shown only; you change it later, in the role’s record.
Sources notice	«Brings N reference sources already in place».	Only appears if the craft brings URLs.

On confirming, the role is created already active and with everything from the craft: mission, guidelines, context, skills and sources. The screen announces «“Job title” is in» and the list reloads.

The role’s internal code is generated for you: the name is used if it is valid, otherwise the craft’s code, and if it already exists a number is appended (_2, _3…). You do not have to decide anything.

From this screen the role is always born active. A role that is pending (status «requested») appears in the org chart with the «pending» mark and has to be signed from its own record. The «Sign» button lives in that record, not here.

How a craft is created and edited

Worth being precise here, because this is the part most often misunderstood:

Creating a role from a craft is what this screen does, with «Add» or «Hire this craft». That is the normal path.
Creating a new craft is not done from the application: there is no form and no button. The catalogue lives in the installation’s code (app/organtia/perfiles.py) and is seeded into the database on startup. Adding a craft means adding its definition there and restarting. On startup, crafts that already exist are not overwritten: only the missing ones are inserted.
Editing a craft is not done from this screen either: there is no edit button and no route that saves it. What you edit is the role you already hired, in its record: there you change job title, mission, rules, context, skills, sources and manager without touching the craft it came from. The role keeps the reference «perfil: código» so you know where it came from.

Put another way: the craft is the mould and is not touched from the interface; the role is the person and you adjust as much as you need.